| 3 | Approval of the Agenda | |
|---|---|---|
| R3-204600 | RAN3#109-e Meeting Agenda | Chairman |
| 4 | Approval of the minutes from previous meetings | |
| R3-204601 | RAN3#108-e Meeting report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-204667 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| R3-205451 | List of E-mail Discussions | RAN3 Chairman |
| R3-205531 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| 8.1 | New Incoming LSs | |
| R3-204608 | Reply LS on port allocation | CT4 |
| R3-204609 | Reply LS on S1/NG DAPS handover | CT |
| R3-204610 | Reply LS on port allocation | CT |
| R3-204611 | LS on port allocation for the W1 interface | CT |
| R3-204612 | LS on updated Rel-16 NR parameter lists | RAN WG1 |
| R3-204613 | Reply LS on QoE Measurement Collection | RAN2 |
| R3-204614 | LS on system support for WUS | RAN2 |
| R3-204615 | Reply LS on the status update of the SON support for NR works | RAN2 |
| R3-204617 | LS on Security Requirements for Sidelink/PC5 Relays | SA2 |
| R3-204619 | LS on the clarification of handover and reselection parameters | 3GPP SA5 |
| R3-204620 | LS on SA5 Rel-17 work on SLA | 3GPP SA5 |
| R3-204621 | LS on mandatory support of full rate user plane integrity protection for 5G | TSG SA |
| R3-204622 | LS on HO to congested cells | SA |
| R3-204642 | Completion of WT-456 and WT-470 | Lincoln Lavoie Broadband Forum (BBF) Technical Committee |
| R3-204668 | Discussion of WUS last used cell issue | Huawei |
| R3-204669 | [DRAFT] Reply LS on assistance indication for WUS | Huawei |
| R3-204714 | On impact in RAN3 of rel-16 user plane integrity protection changes | Qualcomm Incorporated |
| R3-204715 | [DRAFT] Reply LS on mandatory support of full rate user plane integrity protection for 5G | Qualcomm Incorporated |
| R3-204721 | Impact of abnormal UE release on WUS operation | Qualcomm Incorporated |
| R3-204722 | [DRAFT] Reply LS on system support for WUS | Qualcomm Incorporated |
| R3-204741 | HO and reselection parameters for MRO/MLB | ZTE Corporation |
| R3-204742 | Response LS on the clarification of handover and reselection parameters | ZTE Corporation |
| R3-204823 | Alternative QoS Profiles and handover to congested sites | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-204824 | Response LS on HO to congested cells | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-204909 | Discussion on user consent for UE location information | Huawei |
| R3-204910 | Correction to user consent for UE location information | Huawei |
| R3-204911 | Correction to user consent for UE location information | Huawei |
| R3-204912 | Correction to user consent for UE location information | Huawei |
| R3-204913 | Correction to user consent for UE location information | Huawei |
| R3-204914 | [Draft] Reply LS on Reply LS on the status update of the SON support for NR works | Huawei |
| R3-204925 | Further considerations on AQP | Huawei, KPN, Orange, CMCC, China Unicom, BT, Vodafone, TIM |
| R3-204926 | Addition of parameters to Alternative QoS: ARP | Huawei, KPN, Orange, CMCC, China Unicom, BT, Vodafone, TIM |
| R3-204927 | Addition of parameters to Alternative QoS: ARP | Huawei, KPN, Orange, CMCC, China Unicom, BT, Vodafone, TIM |
| R3-204928 | Addition of parameters to Alternative QoS: ARP | Huawei, KPN, Orange, CMCC, China Unicom, BT, Vodafone, TIM |
| R3-204929 | Reply LS on HO to congested cells | Huawei |
| R3-204930 | Addition of parameters to Alternative QoS: MDBV | Huawei, KPN, Orange, CMCC, China Unicom, BT, Vodafone, TIM |
| R3-204931 | Addition of parameters to Alternative QoS: MDBV | Huawei, KPN, Orange, CMCC, China Unicom, BT, Vodafone, TIM |
| R3-204932 | Addition of parameters to Alternative QoS: MDBV | Huawei, KPN, Orange, CMCC, China Unicom, BT, Vodafone, TIM |
| R3-204933 | Clarification of handover and reselection parameters | Huawei |
| R3-204934 | Reply LS on the clarification of handover and reselection parameters | Huawei |
| R3-205174 | Stage2 of User consent for SON based on R3-204615 | ZTE |
| R3-205175 | NGAP signalling of User consent for SON based on R3-204615 | ZTE |
| R3-205176 | XnAP signalling of User consent for SON based on R3-204615 | ZTE |
| R3-205208 | Proposal related to incoming “LS on HO to congested cells” in R3-204622/SP-200587 | VODAFONE Group Plc |
| R3-205463 | LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ON ITS - Connected Automated Vehicles (CAV) | ITU-R Working Party 5A |
| R3-205464 | LS on initiation of new work item Q.IMT2020-SAO “Requirement, framework and protocols for signalling network analyses and optimization in IMT-2020” | ITU-T Study Group 11 |
| R3-205530 | Alternative QoS Profiles and handover to congested sites | Nokia, Nokia Shanghai Bell, Ericsson, Samsung, ZTE, CATT, LG Electronics, InterDigital, Deutsche Telekom |
| R3-205539 | CB: # 55_WUS_LS - Summary of email discussion | Qualcomm - moderator |
| R3-205540 | [DRAFT] Reply LS on system support for WUS | Qualcomm Incorporated |
| R3-205541 | CB: # 56_Rel-16MRO_MLB - Summary of email discussion | Huawei - moderator |
| R3-205542 | Reply LS on the clarification of handover and reselection parameters | Huawei |
| R3-205543 | CB: # 57_UPintProt - Summary of email discussion | Qualcomm - moderator |
| R3-205544 | [DRAFT] Reply LS on mandatory support of full rate user plane integrity protection for 5G | Qualcomm Incorporated |
| R3-205545 | CB: # 58_HO2congestedCells - Summary of email discussion | Nokia - moderator |
| R3-205652 | Reply LS on system support for WUS | Qualcomm Incorporated |
| R3-205653 | Reply LS on mandatory support of full rate user plane integrity protection for 5G | Qualcomm Incorporated |
| 8.2 | LSin received during the meeting | |
| R3-205692 | LS Reply on QoS Monitoring for URLLC | SA5 |
| R3-205781 | Reply LS on assistance indication for WUS | SA2 |
| R3-205782 | Reply LS on early UE capability retrieval for eMTC | RAN2 |
| R3-205791 | Reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | RAN1 |
| 8.3.1 | NR SCG Release for Power Saving | |
| R3-204647 | [Draft] Reply LS on NR SCG release for power saving | ZTE, CATT |
| R3-204680 | Leftover issues on SCG release for UE power saving | Huawei, CATT, ZTE |
| R3-204730 | CR 36.423 for introduction of NR SCG release for power saving | CATT,ZTE,Huawei |
| R3-204731 | CR 38.423 for introduction of NR SCG release for power saving | CATT,ZTE,Huawei |
| R3-204805 | MN Load aware SCG release for power savings in EN-DC | Qualcomm Incorporated |
| R3-204806 | (CR to TS 36.423 X2AP) MN Load aware SCG release for power savings in EN-DC | Qualcomm Incorporated |
| R3-204813 | On Rel-16 UE Power Saving | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-204814 | Support of NR SCG release for power saving | Ericsson, Nokia, Nokia Shangai Bell |
| R3-204815 | Support of NR SCG release for power saving | Ericsson, Nokia, Nokia Shangai Bell |
| R3-204880 | SN release for power saving | NEC, BT |
| R3-204881 | Correction of SN release for power saving | NEC, BT |
| R3-204882 | Correction of SN release for power saving | NEC, BT |
| R3-204959 | Response LS on NR SCG release for power saving | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-205546 | CB: # 59_NR_SCGrelease_pwrSave - Summary of email discussion | Nokia - moderator |
| R3-205764 | Reply LS on NR SCG release for power saving | ZTE, CATT |
| 8.3.2 | IAB Support in NPN Deployments | |
| R3-205290 | Discussion on IAB support in NPN | Huawei |
| R3-205291 | CR for IAB support in NPN | Huawei |
| 8.3.3 | QoS Monitoring for URLLC | |
| R3-204750 | Need of D1 and Reporting interval for Qos monitoring for URLLC | Huawei |
| R3-204751 | Need of D1 and Reporting interval for Qos monitoring for URLLC | Huawei |
| R3-204752 | Need of D1 and Reporting interval for Qos monitoring for URLLC | Huawei |
| R3-204753 | Need of D1 and Reporting interval for Qos monitoring for URLLC | Huawei |
| R3-204754 | Need of D1 and Reporting interval for Qos monitoring for URLLC | Huawei |
| R3-204755 | Need of D1 and Reporting interval for Qos monitoring for URLLC | Huawei |
| R3-205547 | CB: # 60_QoSmonURLLC - Summary of email discussion | Huawei - moderator |
| R3-205739 | Need of D1 and Reporting interval for Qos monitoring for URLLC | Huawei |
| R3-205792 | Need of D1 and Reporting interval for Qos monitoring for URLLC | Huawei |
| R3-205804 | Need of D1 and Reporting interval for Qos monitoring for URLLC | Huawei |
| 9.2 | LTE | |
| R3-205210 | Reporting of SFN time difference in LPPa and NRPPa | Ericsson, NTT DOCOMO, Huawei |
| R3-205211 | Reporting of SFTD measurements in LPPa E-CID measurement results | Ericsson, NTT DOCOMO, Huawei |
| R3-205212 | Reporting of SFTD measurements in LPPa E-CID measurement results | Ericsson, NTT DOCOMO, Huawei |
| R3-205232 | No N26 interface cause value | Ericsson, CMCC |
| R3-205233 | No N26 interface cause value | Ericsson, CMCC |
| R3-205487 | Response to R3-205210 and R3-205211 | Qualcomm Incorporated |
| R3-205560 | No N26 interface cause value | Ericsson, CMCC |
| R3-205561 | No N26 interface cause value | Ericsson, CMCC |
| R3-205583 | CB: # 61_SFN_SFTP_LPPa - Summary of email discussion | Ericsson - moderator |
| R3-205584 | CB: # 62_N26_cause_value - Summary of email discussion | Ericsson - moderator |
| R3-205757 | Support OTDOA assistance data for case of NR serving cell | Qualcomm Incorporated, Ericsson |
| 9.3.1 | NAS Non-Delivery | |
| R3-204825 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-204826 | Response LS on NAS NON Delivery for RRC INACTIVE State | Nokia, Nokia Shanghai Bell, Orange |
| R3-204827 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-204828 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-204988 | Further discussion on NAS Non-Delivery | Huawei |
| R3-204989 | Further discussion on NAS Non-Delivery | Huawei |
| R3-204990 | Further discussion on NAS Non-Delivery | Huawei |
| R3-204991 | [Draft] Reply LS on NAS Non delivery for RRC Inactive state | Huawei |
| R3-204997 | NAS PDU non delivery | Ericsson |
| R3-204998 | NAS PDU handling | Ericsson |
| R3-204999 | NAS PDU handling | Ericsson |
| R3-205000 | NAS PDU handling | Ericsson |
| R3-205001 | NAS PDU handling | Ericsson |
| R3-205132 | Correction of NAS Non Delivery Indication | CATT |
| R3-205133 | Correction to NAS Non Delivery Indication | CATT |
| R3-205134 | Correction to NAS Non Delivery Indication | CATT |
| R3-205562 | CB: # 63_NASnonDelivery - Summary of email discussion | Ericsson - moderator |
| 9.3.2 | Overlapping Band Handling in F1AP | |
| R3-204776 | Overlapping bands handling | Ericsson |
| R3-204777 | Overlapping band handling CR 38.473 | Ericsson |
| R3-204778 | Overlapping band handling CR 38.473 | Ericsson |
| R3-204874 | Discussion on Band and Cell Selection at DU | Nokia, Nokia Shanghai Bell |
| R3-204893 | Discussion on Overlapping Band Handling over F1 | ZTE Corporation |
| R3-204894 | Correction on Overlapping Band Handling over F1 | ZTE Corporation |
| R3-204895 | Correction on Overlapping Band Handling over F1 | ZTE Corporation |
| R3-205274 | Further discussions on overlapping band handling | Huawei |
| R3-205465 | Response to R3-204874 and R3-205274 | L.M. Ericsson Limited |
| R3-205533 | Correction on Overlapping Band Handling over F1 | ZTE Corporation |
| R3-205585 | CB: # 64_OverlappingBandsF1 - Summary of email discussion | ZTE - moderator |
| R3-205673 | Correction on Overlapping Band Handling over F1 | ZTE Corporation |
| R3-205674 | Correction on Overlapping Band Handling over F1 | ZTE Corporation |
| R3-205690 | [draft] Band selection and indication on single connectivity | ZTE |
| R3-205765 | Band selection and indication on single connectivity | ZTE |
| 9.3.3 | DC Operation Mode | |
| R3-204816 | PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-204817 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-204818 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-204819 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-204820 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-204821 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-204822 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-204829 | Support of Cells operating in PSCell/Scell only mode over F1 | Nokia, Nokia Shanghai Bell |
| R3-204830 | Correction of PSCell/SCell only mode | Nokia |
| R3-204831 | Correction of PSCell/SCell only mode | Nokia, Nokia Shanghai Bell |
| R3-204832 | Support of DC Operation Mode over E1 | Nokia, Nokia Shanghai Bell |
| R3-204833 | Support of DC Operation over E1 | Nokia, Nokia Shanghai Bell |
| R3-204834 | Support of DC Operation over E1 | Nokia, Nokia Shanghai Bell |
| R3-205097 | Discussion on NSA mode indication | CATT,China Telecom,ZTE |
| R3-205098 | Correction on NSA mode indication | CATT,China Telecom,ZTE |
| R3-205099 | Correction on NSA mode indication (Rel-16) | CATT,China Telecom,ZTE |
| R3-205100 | Correction on NSA mode indication | CATT,China Telecom,ZTE |
| R3-205101 | Correction on NSA mode indication (Rel-16) | CATT,China Telecom,ZTE |
| R3-205269 | Further discussion on TAC presence over ground interfaces | Huawei |
| R3-205270 | Clarification on TAC presence in Serving Cell Info over F1 | Huawei |
| R3-205271 | Clarification on TAC presence in Serving Cell Info over F1 | Huawei |
| R3-205272 | Clarification on TAC presence in Serving Cell Info over X2 | Huawei |
| R3-205273 | Clarification on TAC presence in Serving Cell Info over X2 | Huawei |
| R3-205525 | Support of Cells operating in PSCell/Scell only mode over F1 | Nokia, Nokia Shanghai Bell, China Telecom, ZTE |
| R3-205526 | Correction of PSCell/SCell only mode | Nokia, Nokia Shanghai Bell, China Telecom, ZTE |
| R3-205527 | Correction of PSCell/SCell only mode | Nokia, Nokia Shanghai Bell, China Telecom, ZTE |
| R3-205563 | CB: # 65_DCoperationMode - Summary of email discussion | Ericsson - moderator |
| R3-205564 | Correction of PSCell/SCell only mode | Nokia, Nokia Shanghai Bell, China Telecom, ZTE |
| R3-205565 | Correction of PSCell/SCell only mode | Nokia, Nokia Shanghai Bell, China Telecom, ZTE |
| R3-205697 | Clarification on TAC presence in Serving Cell Info over X2 | Huawei |
| R3-205698 | Clarification on TAC presence in Serving Cell Info over X2 | Huawei |
| R3-205766 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-205789 | Clarification on TAC presence in Serving Cell Info over X2 | Huawei |
| R3-205790 | Clarification on TAC presence in Serving Cell Info over X2 | Huawei |
| 9.3.4 | Measurement Gap Activation in F1AP | |
| R3-204779 | Measurement gap deactivation over F1AP | Ericsson |
| R3-204892 | Discussion on Measurement Gap Activation over F1 | ZTE Corporation |
| R3-204955 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
| R3-204957 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
| R3-205275 | Further discussions on measurement gap deactivation over F1AP | Huawei |
| R3-205276 | Clarification on measurement gap deactivation over F1AP | Huawei |
| R3-205277 | Clarification on measurement gap deactivation over F1AP | Huawei |
| R3-205566 | CB: # 66_MeasGapActF1AP - Summary of email discussion | Ericsson - moderator |
| R3-205750 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
| R3-205751 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
| R3-205767 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-205768 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-205769 | CB: # 66_MeasGapActF1AP - Summary of email discussion | Ericsson - moderator |
| 9.3.5.1 | Other Corrections | |
| R3-204685 | Correction on AS-rekey and Emergency fallback | Huawei |
| R3-204686 | Correction on AS-rekey and Emergency fallback | Huawei |
| R3-204694 | Update the list of IEs that is not applicable to non-3GPP accesss | Nokia, Nokia Shanghai Bell, Huawei, BT, Intel |
| R3-204695 | Update the list of IEs that is not applicable to non-3GPP accesss | Nokia, Nokia Shanghai Bell, Huawei, BT, Intel |
| R3-204723 | Correction of Downlink Data Delivery Status | Qualcomm Incorporated |
| R3-204736 | Correction on reusing Source TEID at Handover | ZTE |
| R3-204737 | Correction on reusing Source TEID at Handover | ZTE |
| R3-204772 | Correction on configuration update procedure over Xn | ZTE Corporation |
| R3-204773 | Correction on configuration update procedure over Xn | ZTE Corporation |
| R3-204774 | Abnormal conditions on Configuration Update procedure over F1 | ZTE Corporation, CMCC, China Telecom, China Unicom |
| R3-204775 | Abnormal conditions on Configuration Update procedure over F1 | ZTE Corporation, CMCC, China Telecom, China Unicom |
| R3-204780 | Cell Creation Rejection when max number of supported cells is exceeded at CU | Ericsson |
| R3-204781 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson |
| R3-204782 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson |
| R3-204811 | Addition of abnormal conditions in Write-Replace Warning procedure | Nokia, Nokia Shanghai Bell |
| R3-204812 | Addition of abnormal conditions in Write-Replace Warning procedure | Nokia, Nokia Shanghai Bell |
| R3-204835 | Correction of NAS PDU in PDU Session Modify | Nokia, Nokia Shanghai Bell |
| R3-204836 | Correction of NAS PDU is PDU Session Modify | Nokia, Nokia Shanghai Bell |
| R3-204837 | Correction of NAS PDU is PDU Session Modify | Nokia, Nokia Shanghai Bell |
| R3-204853 | Further correction on broadcast PLMN information on F1 | Nokia, Nokia Shanghai Bell |
| R3-204854 | Further correction on PLMN info in Served Cell Information IE | Nokia, Nokia Shanghai Bell |
| R3-204855 | Further correction on PLMN info in Served Cell Information IE | Nokia, Nokia Shanghai Bell |
| R3-204871 | Discussion on SN Terminated (option 3x) GBR bearer establishment | Nokia, Nokia Shanghai Bell |
| R3-204872 | Correction for SN Terminated (option 3x) GBR bearer establishment | Nokia, Nokia Shanghai Bell |
| R3-204873 | Correction for SN Terminated (option 3x) GBR bearer establishment | Nokia, Nokia Shanghai Bell |
| R3-204904 | Correction on UE Context Modification Procedure | CATT, China Telecom |
| R3-204905 | Correction on UE Context Modification Procedure | China Telecom, CATT |
| R3-205002 | Max number of F1-C links is exceeded at CU | Ericsson |
| R3-205003 | Max number of F1-C links is exceeded at CU CR 38.473 | Ericsson |
| R3-205004 | Max number of F1-C links is exceeded at CU CR 38.473 | Ericsson |
| R3-205072 | Correction of S-NSSAI in served cell information | Huawei |
| R3-205073 | Correction of S-NSSAI in served cell information | Huawei |
| R3-205074 | Failure case of user location report | Huawei, Nokia, Nokia Shanghai Bell |
| R3-205075 | Failure case of user location report | Huawei, Nokia, Nokia Shanghai Bell |
| R3-205076 | Multiple location reporting requests and report | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-205077 | Multiple location reporting requests and report | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-205078 | Multiple location reporting requests and report | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-205079 | Multiple location reporting requests and report | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-205080 | Multiple location reporting requests and report | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-205081 | Direct forwarding path availability in Handover Required message | Huawei |
| R3-205082 | Direct forwarding path availability in Handover Required message | Huawei |
| R3-205177 | NGAP cause value for UE context transfer_R15 | ZTE |
| R3-205178 | NGAP cause value for UE context transfer_R16 | ZTE |
| R3-205179 | XnAP cause value for UE context transfer_R15 | ZTE |
| R3-205180 | XnAP cause value for UE context transfer_R16 | ZTE |
| R3-205234 | No N26 interface cause value | Ericsson, CMCC |
| R3-205235 | No N26 interface cause value | Ericsson, CMCC |
| R3-205252 | Correction on the semantics description of the PDCP SN Status Information IE in the DRB Modified List | Samsung |
| R3-205254 | Correction on the semantics description of the PDCP SN Status Information IE in the DRB Modified List | Samsung |
| R3-205343 | Correction for Industrial IoT PDCP duplication for Carrier Aggregation | Intel Corporation, CATT, Huawei, Ericsson |
| R3-205344 | Correction for Industrial IoT PDCP duplication for Carrier Aggregation | Intel Corporation, CATT, Huawei, Ericsson |
| R3-205345 | Correction for Industrial IoT PDCP duplication for Carrier Aggregation | Intel Corporation, CATT, Huawei, Ericsson |
| R3-205346 | Correction for Industrial IoT PDCP duplication for Carrier Aggregation | Intel Corporation, CATT, Huawei, Ericsson |
| R3-205347 | Correction on Industrial IOT PDCP duplication for E1AP | Intel Corporation, ZTE, CATT |
| R3-205348 | Correction on Industrial IOT Rel-15 PDCP duplication for E1AP | Intel Corporation, ZTE, CATT |
| R3-205349 | Correction on Industrial IOT Rel-16 PDCP duplication for E1AP | Intel Corporation, ZTE, CATT |
| R3-205355 | Correction CR on Network instance for 38.413(R15) | CATT |
| R3-205356 | Correction CR on Network instance for 38.423(R15) | CATT |
| R3-205372 | Lossless intra-system HO in disaggregate gNB scenario | Samsung |
| R3-205373 | Correction of intra-system HO in CP-UP seperation scenario | Samsung |
| R3-205374 | Correction of intra-system HO in CP-UP seperation scenario | Samsung |
| R3-205375 | Open issue for Intra-system HO data forwarding for full configuration | Samsung |
| R3-205376 | Correction of Intra-system HO data forwarding for full configuration | Samsung |
| R3-205377 | Correction of Intra-system HO data forwarding for full configuration | Samsung |
| R3-205378 | Correction of Intra-system HO data forwarding over E1 | Samsung |
| R3-205379 | Correction of Intra-system HO data forwarding over E1 | Samsung |
| R3-205380 | Correction of Intra-system HO data forwarding | Samsung |
| R3-205381 | Correction of Intra-system HO data forwarding | Samsung |
| R3-205522 | Cell Creation Rejection when max number of supported cells is exceeded at CU | Ericsson, Verizon Wireless |
| R3-205523 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson, Verizon Wireless |
| R3-205524 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson, Verizon Wireless |
| R3-205567 | Correction for Industrial IoT PDCP duplication for Carrier Aggregation | Intel Corporation, CATT, Huawei, Ericsson |
| R3-205568 | Correction for Industrial IoT PDCP duplication for Carrier Aggregation | Intel Corporation, CATT, Huawei, Ericsson |
| R3-205569 | Correction for Industrial IoT PDCP duplication for Carrier Aggregation | Intel Corporation, CATT, Huawei, Ericsson |
| R3-205570 | Correction for Industrial IoT PDCP duplication for Carrier Aggregation | Intel Corporation, CATT, Huawei, Ericsson |
| R3-205571 | Update the list of IEs that is not applicable to non-3GPP accesss | Nokia, Nokia Shanghai Bell, Huawei, BT, Intel |
| R3-205572 | Update the list of IEs that is not applicable to non-3GPP accesss | Nokia, Nokia Shanghai Bell, Huawei, BT, Intel |
| R3-205573 | CB: # 67_MultiLocRepReq - Summary of email discussion | Huawei - moderator |
| R3-205574 | Multiple location reporting requests and report | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-205575 | Multiple location reporting requests and report | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-205576 | Multiple location reporting requests and report | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-205577 | Multiple location reporting requests and report | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-205578 | Correction on UE Context Modification Procedure | CATT, China Telecom |
| R3-205579 | Correction on UE Context Modification Procedure | China Telecom, CATT |
| R3-205580 | CB: # 68_AS-rekey_emergencyFallback - Summary of email discussion | Huawei - moderator |
| R3-205581 | CB: # 69_DDDS - Summary of email discussion | Qualcomm |
| R3-205582 | CB: # 70_ReuseSrcTEIDatHO - Summary of email discussion | ZTE - moderator |
| R3-205593 | CB: # 71_MaxNofConnectedCells - Summary of email discussion | Ericsson - moderator |
| R3-205594 | Addition of abnormal conditions in Write-Replace Warning procedure | Nokia, Nokia Shanghai Bell |
| R3-205595 | Correction for SN Terminated (option 3x) GBR bearer establishment | Nokia, Nokia Shanghai Bell |
| R3-205596 | Failure case of user location report | Huawei, Nokia, Nokia Shanghai Bell |
| R3-205597 | Failure case of user location report | Huawei, Nokia, Nokia Shanghai Bell |
| R3-205625 | CB: # 75_NAS_PDUcorrection - Summary of email discussion | Nokia - moderator |
| R3-205668 | Correction on reusing Source TEID at Handover | ZTE, Nokia, Nokia Shanghai Bell |
| R3-205669 | Correction on reusing Source TEID at Handover | ZTE, Nokia, Nokia Shanghai Bell |
| R3-205671 | Correction of NAS PDU is PDU Session Modify | Nokia, Nokia Shanghai Bell |
| R3-205672 | Correction of NAS PDU is PDU Session Modify | Nokia, Nokia Shanghai Bell |
| R3-205679 | Correction for SN Terminated (option 3x) GBR bearer establishment | Nokia, Nokia Shanghai Bell |
| R3-205700 | Correction of Downlink Data Delivery Status | Qualcomm Incorporated |
| R3-205702 | Correction of Downlink Data Delivery Status | Qualcomm Incorporated |
| R3-205735 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson, Verizon Wireless |
| R3-205736 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson, Verizon Wireless |
| R3-205763 | Correction for SN Terminated (option 3x) GBR bearer establishment | Nokia, Nokia Shanghai Bell |
| R3-205796 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson, Verizon Wireless |
| 9.3.5.2 | Pure Stage-2 Corrections | |
| R3-204602 | Change of SCTP association when current SCTP association is failed | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-204603 | SCTP association change when current SCTP association is failed (NG) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-204604 | SCTP association change when current SCTP association is failed (NG) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-204605 | SCTP association change when current SCTP association is failed (F1) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-204606 | SCTP association change when current SCTP association is failed (F1) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-204630 | SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| R3-204631 | SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| R3-204632 | SCTP association change when current SCTP association is failed | China Telecom, Nokia, Nokia Shanghai Bell |
| R3-204681 | Correction of F1 procedure in E1 Bearer Context Release scenario | Huawei, China Telecom, CMCC |
| R3-204682 | Correction of F1 procedure in E1 Bearer Context Release scenario | Huawei, China Telecom, CMCC |
| R3-204683 | Correction of UE-associated logical connection for E1 | Huawei, China Telecom, CMCC |
| R3-204684 | Correction of UE-associated logical connection for E1 | Huawei, China Telecom, CMCC |
| R3-204738 | Correction on the usage of SN Reconfiguration Completion | ZTE |
| R3-204739 | CR37340 for correction on the usage of SN Reconfiguration Completion | ZTE |
| R3-204740 | CR37340 for correction on the usage of SN Reconfiguration Completion | ZTE |
| R3-204975 | gNB-CU-UP ID | Ericsson |
| R3-204976 | gNB-CU-UP ID | Ericsson |
| R3-205156 | Correction on NR RRC message transfer to and from the UE | Google Inc. |
| R3-205337 | Adding missing steps querying the source DU’s latest configuration during the inter-gNB-DU mobility for intra-NR | Intel Corporation |
| R3-205338 | Adding missing steps querying the source DU’s latest configuration during the inter-gNB-DU mobility for intra-NR | Intel Corporation |
| R3-205339 | Correction for RRC Reconfiguration Complete Indicator for the first reconfiguration after RRC re-establishment via the last serving gNB-DU | Intel Corporation |
| R3-205340 | Correction for RRC Reconfiguration Complete Indicator for the first reconfiguration after RRC re-establishment via the last serving gNB-DU | Intel Corporation |
| R3-205341 | Correction for intra-gNB-DU handover description | Intel Corporation, CATT |
| R3-205342 | Correction for intra-gNB-DU handover description | Intel Corporation, CATT |
| R3-205460 | ANR enhancement for coexistence of SA and NSA deployment | LG Uplus, LG Electronics, Huawei |
| R3-205461 | Clarification of EN-DC TNL address discovery | LG Uplus, Huawei, Samsung |
| R3-205462 | Clarification of EN-DC TNL address discovery | LG Uplus, Huawei, Samsung |
| R3-205587 | Correction for intra-gNB-DU handover description | Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Google |
| R3-205588 | Correction for intra-gNB-DU handover description | Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Google |
| R3-205589 | Adding missing steps querying the source DU’s latest configuration during the inter-gNB-DU mobility for intra-NR | Intel Corporation, Nokia, Nokia Shanghai Bell, CATT, Google |
| R3-205590 | Adding missing steps querying the source DU’s latest configuration during the inter-gNB-DU mobility for intra-NR | Intel Corporation, Nokia, Nokia Shanghai Bell, CATT, Google |
| R3-205598 | SCTP association change when current SCTP association is failed (NG) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-205599 | SCTP association change when current SCTP association is failed (NG) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-205600 | SCTP association change when current SCTP association is failed (F1) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-205601 | SCTP association change when current SCTP association is failed (F1) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-205602 | SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| R3-205603 | SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| R3-205604 | SCTP association change when current SCTP association is failed | China Telecom, Nokia, Nokia Shanghai Bell |
| R3-205605 | Adding missing steps querying the source DU’s latest configuration during the inter-gNB-DU mobility for intra-NR | Intel Corporation, Nokia, Nokia Shanghai Bell, CATT, Google |
| R3-205678 | SCTP association change when current SCTP association is failed | China Telecom, Nokia, Nokia Shanghai Bell |
| R3-205737 | Correction for intra-gNB-DU handover description | Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Google |
| R3-205738 | Correction for intra-gNB-DU handover description | Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Google |
| R3-205776 | SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| R3-205777 | SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| 10.1 | General | |
| R3-205436 | Work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI | CMCC, Ericsson |
| R3-205445 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-205507 | CB: # 1000_SONMDT_BLCRs - Summary of email discussion | CMCC - moderator |
| R3-205651 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-205654 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-205812 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| 10.2.1.1 | PCI Selection | |
| R3-204756 | PCI selection for NR cells | Huawei |
| R3-204757 | PCI selection for NR cells | Huawei |
| R3-204852 | Detection of PCI conflict | Nokia, Nokia Shanghai Bell |
| R3-204878 | PCI Selection consideration | NEC |
| R3-205129 | Consideration on support of PCI selection | CATT |
| R3-205305 | Discussion on PCI Selection in NR | ZTE |
| R3-205306 | CR for TS38.300 on PCI Selection | ZTE |
| R3-205508 | CB: # 1001_SONMDT_PCISelect - Summary of email discussion | Huawei - moderator |
| R3-205535 | Discussion and solution on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-205536 | Discussion and Solution for Distributed PCI Selection | Ericsson, Verizon Wireless |
| R3-205537 | Discussion and Solution for Centralised PCI Selection | Ericsson, Verizon Wireless |
| R3-205656 | CB: # 1001_SONMDT_PCISelect - Summary of email discussion | Huawei - moderator |
| R3-205694 | TP to 38.300 on PCI Selection | ZTE |
| 10.2.1.2 | Energy Efficiency | |
| R3-204618 | Reply LS on energy efficiency | 3GPP SA5 |
| R3-204767 | Energy efficiency | Huawei |
| R3-204768 | [Draft] Reply LS on reply LS on energy efficiency | Huawei |
| R3-205005 | Energy Efficiency calculations in NG RAN | Ericsson |
| R3-205006 | Reply LS on energy efficiency | Ericsson |
| R3-205307 | Consideration on RAN energy efficiency | ZTE, China Unicom ,China Telecom |
| R3-205308 | CR for TS38.300 on energy efficiency | ZTE, China Unicom ,China Telecom |
| R3-205309 | draft reply LS to SA5 for energy efficiency | ZTE, China Unicom ,China Telecom |
| R3-205509 | CB: # 1002_SONMDT_EnergyEff - Summary of email discussion | Ericsson - moderator |
| R3-205538 | Energy Efficiency calculations in NG RAN | Ericsson |
| R3-205657 | Reply LS on energy efficiency | Ericsson |
| R3-205658 | CB: # 1002_SONMDT_EnergyEff - Summary of email discussion | Ericsson - moderator |
| 10.2.1.3 | Successful Handover Report | |
| R3-204897 | Discussion on support of Successful Handover report | China Telecommunication |
| R3-204935 | Successful Handovers Reports | Huawei |
| R3-205007 | Successful Handover Report CR 38.423 | Ericsson |
| R3-205008 | Successful Handover Report CR 38.473 | Ericsson |
| R3-205009 | Successful Handover Report | Ericsson |
| R3-205421 | NGAP impacts for Successful Handover Report | Samsung |
| R3-205422 | XnAP impacts for Successful Handover Report | Samsung |
| R3-205423 | Discussion for Successful Handover Report | Samsung |
| R3-205510 | CB: # 1003_SONMDT_SuccessHO - Summary of email discussion | Samsung - moderator |
| R3-205627 | LS on Successful Handover Report | Samsung |
| R3-205677 | LS on Successful Handover Report | Samsung |
| R3-205759 | LS on Successful Handover Report | Samsung |
| 10.2.1.4 | UE History Information in EN-DC | |
| R3-204898 | Discussion on support of UE history information | China Telecommunication |
| R3-204936 | UE history information in EN-DC | Huawei |
| R3-205131 | Enhancement of UE history information in EN-DC scenario | CATT |
| R3-205310 | UE History Information in MR-DC | ZTE, Lenovo, Motorola Mobility |
| R3-205311 | 37340 CR for UHI of MR-DC | ZTE |
| R3-205312 | CR for UHI of MR-DC in TS36.423 | ZTE |
| R3-205313 | CR for UHI of MR-DC in TS38.413 | ZTE |
| R3-205314 | CR for UHI of MR-DC in TS38.423 | ZTE |
| R3-205458 | Discussion for UE History Information in EN-DC | BEIJING SAMSUNG TELECOM R&D |
| R3-205459 | X2AP impacts for UE history information in EN-DC | BEIJING SAMSUNG TELECOM R&D |
| R3-205511 | CB: # 1004_SONMDT_UEHist - Summary of email discussion | ZTE - moderator |
| R3-205659 | CB: # 1004_SONMDT_UEHist - Summary of email discussion | ZTE - moderator |
| 10.2.1.5 | Load Balancing Enhancements | |
| R3-204804 | Enhancements to Mobility Settings Change Procedure | Qualcomm Incorporated |
| R3-204937 | Load balancing enhancement | Huawei |
| R3-204938 | Load balancing enhancement | Huawei |
| R3-204978 | Clarification of the use of the TNL load information | Nokia, Nokia Shanghai Bell |
| R3-204979 | Clarification of the TNL Capacity Indicator | Nokia, Nokia Shanghai Bell |
| R3-204980 | Clarification of the TNL Capacity Indicator | Nokia, Nokia Shanghai Bell |
| R3-204981 | Load metric based on PRB occupancy | Nokia, Nokia Shanghai Bell |
| R3-204982 | Load information per slice | Nokia, Nokia Shanghai Bell |
| R3-204983 | Per-slice load status | Nokia, Nokia Shanghai Bell |
| R3-204984 | Per-slice load status | Nokia, Nokia Shanghai Bell |
| R3-205010 | Discussion on further enhancements for MLB in Rel-17 | Ericsson |
| R3-205105 | Discussion on PSCell MLB and SUL PRB usage | CATT |
| R3-205106 | Support of PSCell MLB and SUL PRB usage | CATT |
| R3-205107 | CR on 38.423 for SUL PRB usage | CATT |
| R3-205108 | CR on 38.473 for SUL PRB usage | CATT |
| R3-205109 | CR on 36.423 for PSCell MLB and SUL PRB usage | CATT |
| R3-205250 | Load balancing issue via Xn and F1 | LG Electronics |
| R3-205315 | Discussion on Load Balancing Enhancements | ZTE |
| R3-205316 | CR for TS 36.423 on Load Balancing Enhancements | ZTE |
| R3-205317 | CR for TS 38.423 on Load Balancing Enhancements | ZTE |
| R3-205318 | CR for TS 38.463 on Load Balancing Enhancements | ZTE |
| R3-205319 | CR for TS 38.473 on Load Balancing Enhancements | ZTE |
| R3-205430 | Load balancing enhancements | CMCC |
| R3-205512 | CB: # 1005_SONMDT_LoadBalance - Summary of email discussion | CATT - moderator |
| R3-205660 | CB: # 1005_SONMDT_LoadBalance - Summary of email discussion | CATT - moderator |
| R3-205755 | Clarification of the TNL Capacity Indicator | Nokia, Nokia Shanghai Bell |
| R3-205756 | Clarification of the TNL Capacity Indicator | Nokia, Nokia Shanghai Bell |
| R3-205771 | Clarification of the TNL Capacity Indicator | Nokia, Nokia Shanghai Bell |
| R3-205772 | Clarification of the TNL Capacity Indicator | Nokia, Nokia Shanghai Bell |
| 10.2.1.6 | MRO for SN Change Failure | |
| R3-204896 | Support on MRO for SN Change Failure | China Telecommunication |
| R3-204939 | MRO for SN change failure | Huawei |
| R3-204977 | Detection of wrong SN change | Nokia, Nokia Shanghai Bell |
| R3-205130 | Consideration on support of SN change failure in case of MR-DC | CATT |
| R3-205320 | SN change failure | ZTE |
| R3-205321 | CR for TS 38.300 MRO for SN change failure | ZTE |
| R3-205322 | CR for TS 38.423 MRO for SN change failure | ZTE |
| R3-205386 | MRO for SN Change Failure | Samsung |
| R3-205387 | Support of SN change failure (option 1) | Samsung |
| R3-205388 | Support of SN change failure (option 2) | Samsung |
| R3-205389 | LS on information needed for MRO in SCG Failure Report | Samsung |
| R3-205513 | CB: # 1006_SONMDT_SNChangeFail - Summary of email discussion | Nokia - moderator |
| R3-205661 | CB: # 1006_SONMDT_SNChangeFail - Summary of email discussion | Nokia - moderator |
| 10.2.1.7 | RACH Optimization Enhancements | |
| R3-204633 | Discussion on the PRACH Coordination in Spectrum Shared between LTE and NR | China Telecom,ZTE,Huawei |
| R3-204634 | (TP for [NR_SON_MDT] BL CR for TS 38.423) Addition of LTE PRACH Coordination in XnAP | China Telecommunications |
| R3-204758 | PRACH configuration conflict detection | Huawei |
| R3-204759 | PRACH configuration conflict detection | Huawei |
| R3-205011 | TP for RACH report availability indication on F1 interface | Ericsson |
| R3-205012 | Solution for RACH Conflict Detection and Resolution at gNB-DU | Ericsson |
| R3-205013 | PRACH Configuration of neighbouring cells for EN DC scenario | Ericsson |
| R3-205111 | Discussion on Rel-16 leftover issues for PRACH coordination | CATT |
| R3-205112 | CR on PRACH coordination for F1AP | CATT |
| R3-205113 | CR on PRACH coordination for X2AP | CATT |
| R3-205114 | Discussion on RACH report for SgNB | CATT |
| R3-205115 | LS to RAN2 on RACH report for SgNB | CATT |
| R3-205204 | 2-step RACH Configuration Exchange | Nokia, Nokia Shanghai Bell |
| R3-205205 | RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-205206 | Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-205207 | Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-205323 | Left issue for Rel-16 RACH Optimization | ZTE, China Telecom, China Unicom |
| R3-205514 | CB: # 1007_SONMDT_RACH - Summary of email discussion | Nokia - moderator |
| R3-205647 | LS to RAN2 on RACH report for SgNB | CATT |
| R3-205662 | LS to RAN2 on RACH report for SgNB | CATT |
| R3-205663 | CB: # 1007_SONMDT_RACH - Summary of email discussion | Nokia - moderator |
| 10.2.2 | Coverage and Capacity Optimization | |
| R3-204803 | Coverage and Capacity Optimization | Qualcomm Incorporated |
| R3-204940 | CCO | Huawei |
| R3-204941 | CCO | Huawei |
| R3-205014 | NR CCO – Use cases and tools | Ericsson |
| R3-205015 | NR CCO – Corrective actions | Ericsson |
| R3-205016 | XnAP NR CCO Support | Ericsson |
| R3-205017 | F1AP NR CCO additions for triggered actions | Ericsson |
| R3-205018 | X2AP NR CCO additions for triggered actions | Ericsson |
| R3-205019 | Addition of NR CCO as part of NR SON functions | Ericsson |
| R3-205065 | CCO | Huawei |
| R3-205324 | Discussion on Coverage and Capacity Optimization | ZTE, China Unicom ,China Telecom |
| R3-205325 | CR for TS38.300 on Coverage and Capacity Optimization | ZTE, China Unicom ,China Telecom |
| R3-205326 | CR for TS38.423 on Coverage and Capacity Optimization | ZTE, China Unicom ,China Telecom |
| R3-205327 | CR for TS38.473 on Coverage and Capacity Optimization | ZTE, China Unicom ,China Telecom |
| R3-205390 | CCO baseline solution for NG-RAN | Samsung |
| R3-205391 | Support of CCO function | Samsung |
| R3-205392 | Support of CCO function | Samsung |
| R3-205515 | CB: # 1008_SONMDT_CCO - Summary of email discussion | Qualcomm - moderator |
| R3-205534 | XnAP NR CCO Support | Ericsson |
| R3-205664 | CB: # 1008_SONMDT_CCO - Summary of email discussion | Qualcomm - moderator |
| 10.2.3 | Inter-System Inter-RAT Energy Saving | |
| R3-204764 | Inter-system inter-RAT energy saving | Huawei |
| R3-204765 | Inter-system inter-RAT energy saving | Huawei |
| R3-204766 | Inter-system inter-RAT energy saving | Huawei |
| R3-204802 | Inter-system Energy savings | Qualcomm Incorporated |
| R3-205259 | Discussion on inter-system inter-RAT energy saving | CATT |
| R3-205328 | Consideration on inter-system inter-RAT energy saving | ZTE, China Telecom, China Unicom |
| R3-205329 | CR for TS36.300 on Inter-System Inter-RAT Energy Saving | ZTE, China Telecom, China Unicom |
| R3-205330 | CR for TS38.300 on Inter-System Inter-RAT Energy Saving | ZTE, China Telecom, China Unicom |
| R3-205331 | CR for TS38.413 on Inter-System Inter-RAT Energy Saving | ZTE, China Telecom, China Unicom |
| R3-205419 | NGAP impacts for Inter-System Inter-RAT Energy Saving | Samsung |
| R3-205420 | Discussion for Inter-System Inter-RAT Energy Saving | Samsung |
| R3-205432 | CR to 36.300 for inter-system inter-RAT energy saving | CMCC |
| R3-205434 | CR to 38.300 for inter-system inter-RAT energy saving | CMCC |
| R3-205435 | Support of inter-system inter-RAT energy saving | CMCC |
| R3-205516 | CB: # 1009_SONMDT_InterSystemEnergy - Summary of email discussion | CMCC - moderator |
| R3-205649 | CR to 36.300 for inter-system inter-RAT energy saving | CMCC |
| R3-205650 | CR to 38.300 for inter-system inter-RAT energy saving | CMCC |
| R3-205655 | CB: # 1009_SONMDT_InterSystemEnergy - Summary of email discussion | CMCC - moderator |
| R3-205665 | CR to 36.300 for inter-system inter-RAT energy saving | CMCC |
| R3-205666 | CR to 38.300 for inter-system inter-RAT energy saving | CMCC |
| 10.2.4 | Inter-System Load Balancing | |
| R3-204801 | Inter-system Mobility Load Balancing | Qualcomm Incorporated |
| R3-204942 | inter-system Load balancing | Huawei |
| R3-204943 | inter-system Load balancing | Huawei |
| R3-205020 | Discussion on inter-system MLB for NG-RAN Rel-17 | Ericsson |
| R3-205332 | Discussion on Inter-System Load Balancing | ZTE |
| R3-205333 | CR for TS 38.300 on Inter-System Load Balancing | ZTE |
| R3-205334 | CR for TS 38.413 on Inter-System Load Balancing | ZTE |
| R3-205429 | Inter-system load balancing | CMCC |
| R3-205431 | CR to 36.300 for inter-system load balancing | CMCC |
| R3-205433 | CR to 38.300 for inter-system load balancing | CMCC |
| R3-205517 | CB: # 1010_SONMDT_InterSystemLoad - Summary of email discussion | Ericsson - moderator |
| R3-205667 | CB: # 1010_SONMDT_InterSystemLoad - Summary of email discussion | Ericsson - moderator |
| 10.2.5 | Two-Step RACH Optimization | |
| R3-204760 | RACH optimisation in 2 step RACH | Huawei |
| R3-205021 | 2-step RACH optimization for SON | Ericsson |
| R3-205116 | Discussion on RACH optimisation for 2-step RACH | CATT |
| R3-205117 | LS to RAN2 on RACH report for 2-step RACH | CATT |
| R3-205335 | Initial consideration on Two-Step RACH Optimization for SON | ZTE, China Telecom, China Unicom |
| R3-205437 | 2-step RACH optimisation | CMCC |
| R3-205518 | CB: # 1011_SONMDT_2StepRACH - Summary of email discussion | CATT - moderator |
| R3-205761 | LS to RAN2 on RACH report for 2-step RACH | CATT |
| R3-205762 | CB: # 1011_SONMDT_2StepRACH - Summary of email discussion | CATT - moderator |
| R3-205797 | LS to RAN2 on RACH report for 2-step RACH | CATT |
| 10.2.6 | Mobility Enhancement Optimization | |
| R3-204899 | Discussion on Mobility Enhancement Optimization | China Telecommunication |
| R3-204918 | RLF report for CHO MRO | Lenovo, Motorola Mobility,ZTE |
| R3-204919 | RLF report for DAPS handover | Lenovo, Motorola Mobility, ZTE |
| R3-204944 | Impacts of mobility enhancements | Huawei |
| R3-204985 | Data forwarding in case of a HO to wrong cell | Nokia, Nokia Shanghai Bell |
| R3-204986 | Enabling fetching DL data in case of a HO to wrong cell | Nokia, Nokia Shanghai Bell |
| R3-205022 | Resource optimization for Conditional Handover | Ericsson |
| R3-205023 | Mobility Robustness Optimization for Conditional Handover | Ericsson |
| R3-205024 | Mobility Robustness Optimization for Conditional Handover CR 38.300 | Ericsson |
| R3-205125 | Discussion on MRO for CHO mobility enhance | CATT |
| R3-205126 | Discussion on MRO for DAPS mobility enhance | CATT |
| R3-205336 | Initial consideration on Mobility Enhancement Optimization for SON | ZTE, Lenovo, Motorola Mobility |
| R3-205410 | Discussion on mobility enhancement optimization on DAPS | Samsung |
| R3-205446 | Mobility optimization enhancement | CMCC |
| R3-205519 | CB: # 1012_SONMDT_MobEnh - Summary of email discussion | Lenovo - moderato |
| 10.3.2.1 | MDT Enhancements | |
| R3-204761 | Beam related MDT configuration | Huawei, Deutsche Telekom, BT |
| R3-204762 | Beam related MDT configuration | Huawei, Deutsche Telekom, BT |
| R3-204763 | Beam related MDT configuration | Huawei, Deutsche Telekom, BT |
| R3-205025 | Enabling URI configuration within Trace Activation over S1AP and X2AP | Ericsson |
| R3-205026 | Enabling URI configuration within Trace activation over S1AP | Ericsson |
| R3-205027 | Enabling URI configuration within Trace activation over X2AP | Ericsson |
| R3-205028 | Beam measurement inclusion in M1 measureurement of immediate MDT | Ericsson |
| R3-205029 | Beam measurement inclusion in M1 measureurement of immediate MDT for NGAP | Ericsson |
| R3-205453 | MDT Enhancements coexistence with IDC | ZTE |
| R3-205454 | MDT coexistence with IDC CR for 38.401 | ZTE |
| R3-205455 | MDT coexistence with IDC CR for E1AP | ZTE |
| R3-205456 | MDT coexistence with IDC CR for F1AP | ZTE |
| R3-205520 | CB: # 1013_SONMDT_MDTEnh - Summary of email discussion | Ericsson - moderator |
| R3-205793 | [draft] LS on URI for streaming trace reporting in LTE | Ericsson |
| R3-205798 | LS on URI for streaming trace reporting in LTE | Ericsson |
| 10.3.2.2 | MDT for MR-DC | |
| R3-204906 | MDT in MR-DC | Huawei |
| R3-204907 | MDT in MR-DC | Huawei |
| R3-204908 | MDT in MR-DC | Huawei |
| R3-205260 | Support of MDT for MR-DC | CATT |
| R3-205457 | R3-20xxxx L2 measurement | ZTE |
| R3-205521 | CB: # 1014_SONMDT_MDTMR-DC - Summary of email discussion | Huawei - moderator |
| R3-205741 | CB: # 1014_SONMDT_MDTMR-DC - Summary of email discussion | Huawei - moderator |
| R3-205743 | MDT in MR-DC | Huawei |
| 13.1 | General | |
| R3-204794 | Work plan for Rel-17 IAB | Qualcomm Incorporated (WI Rapporteur) |
| 13.2.1 | Inter-Donor IAB Node Migration | |
| R3-204660 | Considerations on reducing signal overhead during Inter-donor IAB node migration | KDDI Corporation |
| R3-204698 | Considerations on differentiation inter-donor/intra-donor migration | KDDI Corporation |
| R3-204732 | Discussion on inter IAB donor-CU topology adaptation | CATT |
| R3-204733 | Discussion on group handover in inter IAB donor | CATT |
| R3-204745 | Inter-CU topology adaptation procedure | Intel Corporation |
| R3-204795 | IAB inter-donor IAB-node migration | Qualcomm Incorporated |
| R3-204917 | Inter-Donor CU topology adaptation | Lenovo,Motorola Mobility |
| R3-205162 | Discussion on inter-donor IAB-node migration procedure | ZTE, Sanechips |
| R3-205221 | Inter-donor Migration in IAB Networks – General Principles | Ericsson |
| R3-205222 | Inter-donor Migration Mechanism in IAB Networks | Ericsson |
| R3-205251 | Issue on inter-donor IAB-node migration | LG Electronics |
| R3-205264 | Discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| R3-205292 | Inter-CU handover procedure analysis | Huawei |
| R3-205294 | CHO and DAPS in R17 IAB | Huawei |
| R3-205352 | Considerations on IAB-DU configuration update during Inter-CU migration | ZTE, Sanechips |
| R3-205411 | Discussion on inter-donor IAB node migration | Samsung |
| R3-205466 | CB: # 6_IAB_Inter-DonorMigration - Summary of email discussion | Ericsson - moderator |
| 13.2.2 | Reduction of Service Interruption | |
| R3-204734 | Discussion on reducing the service interruption for IAB | CATT |
| R3-204796 | Enhancements to intra-donor IAB-node-migration | Qualcomm Incorporated |
| R3-205063 | Consideration on IAB Node Migration for Mobile Scenarios | LG Electronics |
| R3-205163 | Discussion on service interruption reduction in IAB node migration | ZTE, Sanechips |
| R3-205164 | Consideration on R17-IAB mobility enhancement | ZTE, Sanechips |
| R3-205223 | Handling of In-flight Packets at Handover in IAB Networks | Ericsson |
| R3-205249 | Consideration on RLF Recovery | LG Electronics |
| R3-205293 | Inter-CU RLF recovery procedure | Huawei |
| R3-205412 | Discussion on Service Interruption Reduction in IAB | Samsung |
| R3-205413 | CR on service interruption reduction for intra-CU IAB migration | Samsung |
| R3-205425 | Inter-CU BH RLF recovery procedure for IAB node | Huawei |
| R3-205467 | CB: # 7_IAB_ServiceInterruptionReduction - Summary of email discussion | Qualcomm - moderator |
| 13.2.3 | Topology Redundancy | |
| R3-204746 | Multi-route support in IAB | Intel Corporation |
| R3-204797 | IAB-enhancements for topological redundancy | Qualcomm Incorporated |
| R3-204867 | Separation of CP/UP for improved CP robustness | AT&T |
| R3-205064 | Consideration on topological redundancy | LG Electronics |
| R3-205167 | Considerations on CP/UP separation | ZTE, Sanechips |
| R3-205224 | Multi-connectivity for IAB Nodes | Ericsson |
| R3-205265 | discussion on Inter-CU topology redundancy | Nokia, Nokia Shanghai Bell |
| R3-205295 | Discussion on IAB topological redundancy | Huawei |
| R3-205296 | Routing enhancement for IAB | Huawei |
| R3-205414 | Discussion on topology redundancy in IAB | Samsung |
| R3-205415 | CR on CP-UP separation over Xn (Rel-17) | Samsung |
| R3-205468 | C5686B: # 8_IAB_TopologyRedundancy - Summary of email discussion | Nokia - moderator |
| 13.3.1 | Congestion Mitigation | |
| R3-204747 | Enhancement to IAB DL Flow Control | Intel Corporation |
| R3-204798 | IAB flow and congestion control enhancements | Qualcomm Incorporated |
| R3-204868 | Congestion Indication to CU-CP | AT&T |
| R3-205169 | Consideration on R17-IAB E2E flow control | ZTE, Sanechips |
| R3-205225 | Downlink End-to-End Flow Control in IAB Networks | Ericsson |
| R3-205297 | Discussion on IAB E2E flow control | Huawei |
| R3-205416 | Discussion on Congestion Mitigation in IAB | Samsung |
| R3-205469 | CB: # 9_IAB_CongestionMitigation - Summary of email discussion | Ericsson - moderator |
| 13.3.2 | Multi-Hop Performance: QoS, Latency, Fairness | |
| R3-204735 | Consideration on Multi-Hop Performance: QoS, Latency, Fairness | CATT |
| R3-204799 | Simulations on fairness support in IAB topology | Qualcomm Incorporated |
| R3-205168 | Consideration on multi-hop latency for IAB network | ZTE, Sanechips |
| R3-205170 | Discussion on fairness in IAB scheduling | ZTE, Sanechips |
| R3-205417 | Discussion on latency reduction in IAB | Samsung |
| R3-205418 | Discussion on PDCP duplication support in IAB | Samsung |
| R3-205470 | CB: # 10_IAB_MultiHopPerf - Summary of email discussion | CATT - moderator |
| R3-205742 | CB: # 10_IAB_MultiHopPerf - Summary of email discussion | CATT - moderator |
| 13.4.1 | CLI Management | |
| R3-204869 | Support for CLI management by IAB nodes | AT&T |
| R3-205226 | CLI Management Support for IAB | Ericsson |
| R3-205471 | CB: # 11_IAB_CLImgmt - Summary of email discussion | AT&T - moderator |
| 13.4.2 | Others | |
| R3-204870 | Support for IAB resource multiplexing enhancements | AT&T |
| R3-205171 | Discussion on IAB duplexing enhancements | ZTE, Sanechips |
| R3-205488 | CB: # 13_IAB_MPXenh - Summary of email discussion | ZTE - moderator |
| R3-205733 | CB: # 13_IAB_MPXenh - Summary of email discussion | ZTE - moderator |
| R3-205749 | LS on intra-frequency operation in NR DC for IAB node | ZTE |
| R3-205775 | LS on intra-frequency operation in NR DC for IAB node | ZTE |
| 13.5 | Others | |
| R3-204800 | IAB support for RAN shared between PLMN and NPN | Qualcomm Incorporated |
| R3-205172 | Discussion on RAN-sharing in IAB network | ZTE, Sanechips |
| R3-205472 | CB: # 12_IAB_Others_RANsharing - Summary of email discussion | ZTE - moderator |
| R3-205732 | CB: # 12_IAB_Others_RANsharing - Summary of email discussion | ZTE - moderator |
| 15.1 | General | |
| R3-204643 | Time plan for NR QoE Management and Optimizations for Diverse Services | China Unicom |
| R3-204644 | TR Skeleton for NR QoE Management and Optimizations for Diverse Services | China Unicom |
| R3-204645 | Time plan for NR QoE Management and Optimizations for Diverse Services | China Unicom |
| R3-204646 | Time plan for NR QoE Management and Optimizations for Diverse Services | China Unicom |
| R3-205478 | CB: # NRQoE1-Workplan_TRSkeleton - Summary of email discussion | China Unicom - moderator |
| R3-205722 | Time plan for NR QoE Management and Optimizations for Diverse Services | China Unicom |
| R3-205723 | TR Skeleton for NR QoE Management and Optimizations for Diverse Services | China Unicom |
| R3-205816 | TR Skeleton for NR QoE Management and Optimizations for Diverse Services | China Unicom, ZTE |
| 15.2 | Triggering, Configuring, Measurement Collection and Reporting | |
| R3-204706 | QoE Configuration and reporting | Qualcomm Incorporated |
| R3-204707 | QoE handling in handover | Qualcomm Incorporated |
| R3-204708 | Interworking with LTE QoE | Qualcomm Incorporated |
| R3-204851 | Framework for QoE measurement collection | Nokia, Nokia Shanghai Bell |
| R3-205181 | Initial Consideration On Study of NR QoE | ZTE |
| R3-205182 | TP for FS_NR_QoE | ZTE |
| R3-205183 | Consideration on slice QoE measurement | ZTE |
| R3-205200 | pCR for TR 38.8xx: NR QoE Management Framework | Ericsson |
| R3-205201 | pCR for TR 38.8xx: NR QoE Measurement Triggering, Configuration, Collection and Reporting | Ericsson |
| R3-205202 | pCR for TR 38.8xx: Use Cases for NR QoE Management | Ericsson |
| R3-205281 | NR QoE measurement overview | Huawei |
| R3-205283 | Potential RAN3 impacts about QoE measurement | Huawei |
| R3-205359 | Discussion on NR QoE solution for various service | CATT |
| R3-205360 | Discussion on NR QoE solution architecture and interface impact | CATT |
| R3-205370 | Some Considerations on QOE Collection in NR | China Telecommunications |
| R3-205402 | Discussion on NR QoE requirements and potential solutions | Samsung |
| R3-205403 | Discussion on NR QoE interface impact and solutions | Samsung |
| R3-205439 | NR QoE management | CMCC |
| R3-205479 | CB: # NRQoE2-Services - Summary of email discussion | ZTE - moderator |
| R3-205480 | CB: # NRQoE2-Solutions - Summary of email discussion | Ericsson - moderator |
| R3-205695 | New service type of NR QoE | ZTE |
| R3-205696 | TP for TR38.890 on 5G services | ZTE |
| R3-205724 | New service type of NR QoE | ZTE |
| R3-205725 | TP for TR38.890 on 5G services | ZTE |
| R3-205726 | CB: # NRQoE2-Solutions - Summary of email discussion | Ericsson - moderator |
| R3-205785 | LS on Transport of NR QoE Reports in the RAN | Ericsson |
| 15.3 | Others | |
| R3-205282 | Initial discussion on latency measurement | Huawei |
| R3-205481 | CB: # NRQoE3-Others - Summary of email discussion | Huawei - moderator |
| 17.1 | General | |
| R3-204838 | Framework for Skeleton for Slice Continuity | Nokia, Nokia Shanghai Bell |
| R3-205428 | Skeleton for TR 38.832 v0.0.0 | CMCC, ZTE |
| R3-205442 | Work plan for RAN slicing SI | CMCC, ZTE |
| R3-205482 | CB: # RANSlicing1-Workplan_TRSkeleton - Summary of email discussion | CMCC, ZTE - moderator |
| R3-205815 | Skeleton for TR 38.832 v0.0.0 | CMCC, ZTE |
| 17.2 | Mechanisms to Support Service Continuity | |
| R3-204807 | Service Continuity when a slice becomes unavailable | Qualcomm Incorporated |
| R3-204808 | LS on Service Continuity when a slice becomes unavailable | Qualcomm Incorporated |
| R3-204839 | Use Cases for Network Slice Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-204840 | RAN Re-mapping Solution: key principles | Nokia, Nokia Shanghai Bell |
| R3-204883 | On RAN slice awareness and service continuity | NEC |
| R3-204884 | On intra-RAT handover service continuity | NEC |
| R3-204902 | Discussion on slice re-mapping and fallback upon handover | China Telecommunication |
| R3-205030 | Discussion on slice Re-mapping at mobility | Ericsson |
| R3-205061 | Description of Slice Remapping | Ericsson |
| R3-205083 | Use cases for network slice service continuity | Huawei |
| R3-205084 | Potential solutions to network slice service continuity | Huawei |
| R3-205184 | Initial Consideration On RAN slicing | ZTE, Lenovo, Motorola Mobility |
| R3-205185 | TP for 38.832 | ZTE |
| R3-205353 | Discussion on use cases for slice service continuity and slice remapping solutions | LG Electronics |
| R3-205354 | (TP for 38.832) Use cases for slice service continuity and slice remapping solutions | LG Electronics |
| R3-205361 | Discussion on NG based handover slice re-mapping | CATT |
| R3-205362 | Discussion on Xn based handover slice re-mapping | CATT |
| R3-205404 | Discussion on slice re-mapping | Samsung |
| R3-205440 | Service continuity for slicing | CMCC |
| R3-205441 | TP to service continuity for slicing | CMCC |
| R3-205483 | CB: # RANSlicing2-Slice_Remapping_Scenarios - Summary of email discussion | ZTE - moderator |
| R3-205484 | CB: # RANSlicing3-Slice_Remapping_Solutions - Summary of email discussion | Nokia - moderator |
| R3-205626 | (TP for 38.832) Re-mapping Policy in target NG-RAN node | Nokia |
| R3-205646 | (TP for 38.832) Potential solutions to network slice service continuity | Huawei |
| R3-205689 | TP for TR38.382 on service continuity for slicing | CMCC |
| R3-205727 | TP for TR38.382 on service continuity for slicing | CMCC |
| R3-205728 | CB: # RANSlicing2-Slice_Remapping_Scenarios - Summary of email discussion | ZTE - moderator |
| R3-205729 | (TP for 38.832) Potential solutions to network slice service continuity | Huawei |
| R3-205730 | CB: # RANSlicing3-Slice_Remapping_Solutions - Summary of email discussion | Nokia - moderator |
| R3-205758 | LS on Enhancement of RAN Slicing | Qualcomm |
| R3-205783 | TP for TR38.382 on service continuity for slicing | CMCC |
| R3-205802 | LS on Enhancement of RAN Slicing | Qualcomm |
| 17.3 | Others | |
| R3-204809 | On need for UE Capability Check for RAN slicing | Qualcomm Incorporated |
| R3-205031 | Reasons and methods for serving slices on different frequencies | Ericsson |
| R3-205085 | General overview of RAN3 impact of SA2 slicing work | Huawei |
| R3-205186 | SA2 impact on RAN3 part | ZTE |
| R3-205485 | CB: # RANSlicing4-Slices_onFrequencies - Summary of email discussion | Ericsson - moderator |
| R3-205486 | CB: # RANSlicing5-SA2impact - Summary of email discussion | Huawei - moderator |
| R3-205703 | TP on solutions for serving slices on different frequencies | Ericsson |
| 19.1 | General | |
| R3-204623 | Introduction of NR Positioning in NRPPa | Ericsson LM |
| R3-204624 | Positioning support over F1AP | Huawei Technologies (Korea) |
| R3-204625 | Introduction of positioning support over F1AP | Qualcomm Incorporated |
| R3-204626 | Support for UL NR E-CID | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm |
| R3-204628 | Positioning support over F1AP | Huawei Technologies (Korea) |
| R3-204629 | Update of the NRPPa Transport procedure to support NR positioning | Nokia, Nokia Shanghai Bell |
| R3-204966 | (TP for BL CR for TS 38.305) Correct on NRPPa procedure description | Huawei, Ericsson, Intel |
| R3-204967 | (TP for BL CR for TS 38.305) Correction on gNB and LMF information transfer | Huawei, Ericsson, Intel |
| R3-204968 | (TP for BL CR for TS 38.470) Positioning support over F1AP | Huawei |
| R3-204971 | (TP for BL CR for TS 38.473) correction and update of F1AP | Huawei, Ericsson, Intel, Qualcomm Incorporated, Nokia |
| R3-205153 | (TP to BL CR for TS 38.455) Correction and update of NRPPa | Ericsson, Qualcomm Incorporated, Huawei, Intel, Nokia, Nokia Shanghai Bell |
| R3-205214 | TP to NRPPa: correction of NOTE in architecture figure in TS 38.305 | Ericsson, Huawei |
| R3-205473 | CB: # 1_R16Pos_BLCRs - Summary of email discussion | Intel - moderator |
| R3-205551 | Introduction of NR Positioning in NRPPa | Ericsson LM |
| R3-205552 | Introduction of positioning support over F1AP | Qualcomm Incorporated |
| R3-205553 | (TP for BL CR for TS 38.305) Correct on NRPPa procedure description | Huawei, Ericsson, Intel |
| R3-205554 | TP to NRPPa: correction of NOTE in architecture figure in TS 38.305 | Ericsson, Huawei |
| R3-205555 | (TP for BL CR for TS 38.470) Positioning support over F1AP | Huawei |
| R3-205628 | [Draft] LS to RAN2 | Intel |
| R3-205638 | CB: # 1_R16Pos_BLCRs - Summary of email discussion | Intel - moderator |
| R3-205642 | Support for UL NR E-CID | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm |
| R3-205719 | LS on the NOTE in architecture figure in TS 38.305 | Intel |
| R3-205805 | Positioning support over F1AP | Huawei Technologies (Korea) |
| R3-205806 | Positioning support over F1AP | Huawei Technologies (Korea) |
| R3-205807 | Update of the NRPPa Transport procedure to support NR positioning | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Intel, Qualcomm Incorporated |
| R3-205808 | Introduction of NR Positioning in NRPPa | Ericsson, Intel, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-205809 | Introduction of positioning support over F1AP | Qualcomm Incorporated, Huawei, Ericsson, Intel, Nokia, Nokia Shanghai Bell |
| R3-205811 | Support for UL NR E-CID | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Intel, Qualcomm |
| 19.2 | NRPPa Issues | |
| R3-204627 | Update of the NRPPa Transport procedure to support NR positioning | Nokia, Nokia Shanghai Bell |
| R3-204743 | (TP for NRPPa BL CR on 38.455) Report NR/EUTRAN CGI in Other-RAT measurement result | NTT DOCOMO INC. |
| R3-204969 | (TP to BL CR for TS 38.455) Completion of NRPPa | Huawei |
| R3-204970 | (TP for BL CR for TS 38.455) Support of aperiodic SRS | Huawei |
| R3-205146 | (TP to BL CR TS 38.455) Addition of missing parameters | Qualcomm Incorporated |
| R3-205215 | TP to NRPPa: Further corrections on TRP List and AP SRS | Ericsson |
| R3-205216 | TP to NRPPa: addition of Search Window Parameters | Ericsson |
| R3-205288 | (TP to NRPPa BLCR for TS38.455) NRPPa Left Issues for NR positioning | ZTE Corporation |
| R3-205474 | CB: # 2_R16Pos_NRPPa - Summary of email discussion | Ericsson - moderator |
| R3-205629 | TP to NRPPa: addition of Search Window Parameters | Ericsson |
| R3-205630 | (TP to BL CR for TS 38.455) Completion of NRPPa | Huawei |
| R3-205631 | (TP for BL CR for TS 38.455) Support of aperiodic SRS | Huawei |
| R3-205632 | (TP for NRPPa BL CR on 38.455) Report NR/EUTRAN CGI in Other-RAT measurement result | NTT DOCOMO INC. |
| R3-205633 | (TP to BL CR TS 38.455) Addition of missing parameters | Qualcomm Incorporated |
| R3-205634 | (TP to BL CR for TS 38.455) Positioning abort | Huawei |
| R3-205637 | CB: # 2_R16Pos_NRPPa - Summary of email discussion | Ericsson - moderator |
| R3-205784 | (TP for BL CR for TS 38.455) Support of aperiodic SRS | Huawei |
| R3-205786 | (TP to BL CR for TS 38.455) Completion of NRPPa | Huawei |
| 19.3 | F1AP Issues | |
| R3-204749 | (TP to BL CR for TS 38.401): positioning procedures in split gNB | Intel Corporation |
| R3-204791 | (TP for NR_POS BL CR for TS 38.473) Support for UL NR E-CID | Nokia, Nokia Shanghai Bell, Huawei |
| R3-204792 | (TP for NR_POS BL CR for TS 38.473) F1AP Open Issues | Nokia, Nokia Shanghai Bell |
| R3-204972 | (TP to BL CR for TS 38.473) Completion of F1AP | Huawei |
| R3-204973 | (TP for BL CR for TS 38.473) Introduce Positining Information Update procedure | Huawei |
| R3-205147 | (TP to BL CR TS 38.473) Addition of missing parameters | Qualcomm Incorporated |
| R3-205217 | TP to F1AP: Further corrections on TRP List and AP SRS | Ericsson |
| R3-205218 | TP to F1AP: addition of Search Window Parameters | Ericsson |
| R3-205289 | (TP to F1AP BLCR for TS38.473) Correction of F1AP FFSs for NR positioning | ZTE Corporation |
| R3-205475 | CB: # 3_R16Pos_F1AP - Summary of email discussion | Huawei - moderator |
| R3-205635 | (TP to BL CR for TS 38.401): positioning procedures in split gNB | Intel Corporation |
| R3-205636 | CB: # 3_R16Pos_F1AP - Summary of email discussion | Huawei - moderator |
| R3-205670 | (TP to F1AP BLCR for TS38.473) F1 corrections and NRPPa alignment | Huawei |
| R3-205740 | (TP for BL CR for TS 38.473) Introduce Positining Information Update procedure | Huawei |
| 19.4 | Others | |
| R3-204748 | (TP to BL CR for TS 38.305): stage-2 corrections for positioning | Intel Corporation, Huawei |
| R3-204974 | (TP to BL CR for TS 38.473) Correction on the Measurement ID | Huawei |
| R3-205213 | TP to NRPPa: support of SFTD measurements transfer to LMF | Ericsson, Huawei |
| R3-205219 | TP to NRPPa: correction of TRP geo-coordinates | Ericsson |
| R3-205220 | TP to F1AP: correction of TRP geo-coordinates | Ericsson |
| R3-205476 | CB: # 4_R16Pos_Others - Summary of email discussion | Huawei - moderator |
| R3-205639 | (TP to BL CR for TS 38.305): stage-2 corrections for positioning | Intel Corporation, Huawei |
| R3-205640 | CB: # 4_R16Pos_Others - Summary of email discussion | Huawei - moderator |
| R3-205644 | TP to NRPPa: correction of TRP geo-coordinates | Ericsson |
| R3-205645 | TP to F1AP: correction of TRP geo-coordinates | Ericsson |
| R3-205744 | (TP to BL CR for TS 38.305): stage-2 corrections for positioning | Intel Corporation, Huawei |
| R3-205773 | TP to NRPPa: correction of TRP geo-coordinates | Ericsson |
| R3-205774 | TP to F1AP: correction of TRP geo-coordinates | Ericsson |
| 20.1 | General | |
| R3-205165 | NR_NTN_solutions work plan | THALES |
| R3-205166 | NR NTN Reference scenarios definition for Rel-17 normative phase | THALES |
| R3-205489 | CB: # 33_NTN_General - Summary of email discussion | Thales - moderator |
| R3-205680 | CB: # 33_NTN_General - Summary of email discussion | Thales - moderator |
| 20.2.1 | Network Identifier Handling | |
| R3-204616 | LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | SA2 |
| R3-204662 | Initial Thoughts on NTN Relevant ID Handling | ZTE |
| R3-204687 | NR-NTN: Network Identities Handling | Fraunhofer IIS, Fraunhofer HHI |
| R3-204719 | Discussion of SA2 LS on architecture aspects for using satellite access in 5G | Qualcomm Incorporated |
| R3-204720 | [DRAFT] Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | Qualcomm Incorporated |
| R3-204961 | Discussion on Network IDs handling for NTN | Huawei |
| R3-205118 | Discussion on identifier handling in NTN | CATT |
| R3-205139 | Discussion on identifier handling in NTN | CATT |
| R3-205155 | Tracking Area Handling with NTN | Ericsson LM |
| R3-205157 | Tracking Area Handling with NTN - XnAP | Ericsson LM |
| R3-205266 | Discussion on network identities handling | Nokia, Nokia Shanghai Bell |
| R3-205393 | Network Identifier Handling | Samsung |
| R3-205427 | Proposal related to incoming LS on “...architecture aspects for using satellite access in 5G” in R3-204616/S2-2004688 | VODAFONE Group Plc |
| R3-205438 | Discussion on key issues in NTN | CMCC |
| R3-205490 | CB: # 35_NTN_SA2LS - Summary of email discussion | Qualcomm - moderator |
| R3-205491 | CB: # 34_NTN_nwID_handling - Summary of email discussion | Nokia - moderator |
| R3-205681 | [DRAFT] Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | Qualcomm Incorporated |
| R3-205795 | Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | Qualcomm Incorporated |
| 20.2.2 | Registration Update and Paging Handling | |
| R3-204663 | Initial Thoughts on NTN UE Registration and Paging | ZTE |
| R3-204962 | Discussion on Registration Update and Paging Handling for NTN | Huawei |
| R3-204963 | Support Non-Terrestrial Networks | Huawei |
| R3-205394 | More consideration for paging UE in NTN | Samsung |
| R3-205449 | Discussion on Registration Update and Paging Handling | CATT |
| R3-205452 | CR for Paing UE per SSB beam | Samsung |
| R3-205492 | CB: # 36_NTN_RAU_Paging - Summary of email discussion | Samsung - moderator |
| R3-205682 | Support Non-Terrestrial Networks | Huawei |
| R3-205683 | CB: # 36_NTN_RAU_Paging - Summary of email discussion | Samsung - moderator |
| R3-205779 | Support Non-Terrestrial Networks | Huawei |
| R3-205780 | Support Non-Terrestrial Networks | Huawei |
| R3-205814 | Support Non-Terrestrial Networks | Huawei |
| 20.2.3 | Cell Relation Handling | |
| R3-204664 | Initial Thoughts on NTN Cell Relation Handling | ZTE |
| R3-204665 | Initial Thoughts on NTN Cell Relation Handling | ZTE |
| R3-204964 | Discussion on cell relation for NTN | Huawei |
| R3-205119 | Discussion on cell relation handling in NTN | CATT |
| R3-205140 | Discussion on cell relation handling in NTN | CATT |
| R3-205267 | Discussion on the PCI issue between HAPS and terrestrial networks | Nokia, Nokia Shanghai Bell |
| R3-205493 | CB: # 37_NTN_CellRelation - Summary of email discussion | ZTE - moderator |
| 20.2.4 | Feeder Link Switch-Over for LEO | |
| R3-204666 | Initial Thoughts on NTN LEO Feeder Link Switch-Over | ZTE |
| R3-204965 | Discussion on feeder link switch for NTN | Huawei |
| R3-205159 | Supporting Feeder Link Switchover | Ericsson LM |
| R3-205160 | Support for Feeder Link Switchover for Transparent Architecture | Ericsson LM |
| R3-205161 | Feeder Link Switchover for Transparent NTN - Stage 2 | Ericsson LM |
| R3-205173 | On NTN Feeder link switch over | THALES |
| R3-205395 | Discussion for the served UE during feeder link switch over | Samsung |
| R3-205405 | Discussion on RACH issue in feeder link switch over | Samsung |
| R3-205450 | Discussion on Feeder Link Switch | CATT |
| R3-205494 | CB: # 38_NTN_FeederSwitch - Summary of email discussion | Ericsson - moderator |
| 22.1 | General | |
| R3-204688 | Work Plan for Rel-17 NR Multicast and Broadcast Services | Huawei, CMCC |
| R3-204841 | 5MBS Scope and Structuring of RAN3 work | Nokia, Nokia Shanghai Bell |
| R3-204842 | Introduction of 5MBS | Nokia, Nokia Shanghai Bell |
| R3-205495 | CB: # 14_MBS_General - Summary of email discussion | Huawei - moderator |
| R3-205586 | Introduction of NR MBS | Huawei |
| R3-205641 | Introduction of NR MBS Service | Nokia, Nokia Shanghai Bell |
| R3-205684 | Introduction of NR MBS | Huawei |
| R3-205810 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-205813 | Introduction of NR MBS | Huawei, CMCC |
| 22.2 | Necessary Enhancements to NG-RAN Architecture | |
| R3-204648 | Discussion on the NG-RAN architecture enhancement for MBS | ZTE |
| R3-204649 | Discussion on the split gNB architecture enhancement for MBS | ZTE |
| R3-204650 | [Draft] LS on NR Multicast and Broadcast Services | ZTE |
| R3-204689 | NG-RAN Architecture to support NR MBS | Huawei |
| R3-204702 | 5G MBS RAN Architecture | Qualcomm Incorporated |
| R3-204703 | QoS/bearer model and session management | Qualcomm Incorporated |
| R3-204744 | MBS architecture discussion | Intel Corporation |
| R3-204843 | Enhancements to NG-RAN architecture for 5MBS | Nokia, Nokia Shanghai Bell |
| R3-204885 | Overview of NR MBS | vivo |
| R3-204920 | Overview on NG RAN to support NR Multicast and Broadcast Services | Lenovo, Motorola Mobility |
| R3-205032 | On NG-RAN Architecture for 5G MBS | Ericsson |
| R3-205141 | Discussion on MBS session management | CATT |
| R3-205203 | [TP for BL CR for 38.401] Overall NG-RAN architecture for NR MBS | Ericsson |
| R3-205364 | NG-RAN Architecture Discussion for MBS | CATT |
| R3-205396 | Necessary Enhancements to NG-RAN Architecture | Samsung |
| R3-205397 | Addition of MBS feature | Samsung |
| R3-205444 | Requirements and NG-RAN architecture to support MBS | CMCC |
| R3-205496 | CB: # 15_MBS_Architecture - Summary of email discussion | Huawei - moderator |
| R3-205497 | CB: # 16_MBS_Bearers_SessionMgmt - Summary of email discussion | Qualcomm - moderator |
| 22.3.1 | Basic Mobility with Service Continuity | |
| R3-204690 | Service continuity Scenarios during mobility for MBS | Huawei, LGU+ |
| R3-204691 | Service continuity CP and UP aspects during mobility | Huawei, LGU+ |
| R3-204704 | MBS Service continuity | Qualcomm Incorporated |
| R3-204844 | 5MBS Control Plane impact of mobility with service continuity | Nokia, Nokia Shanghai Bell |
| R3-204845 | 5MBS User Plane impact of mobility with service continuity | Nokia, Nokia Shanghai Bell |
| R3-204922 | Support of Loss-less handover for 5G MBS | Lenovo, Motorola Mobility |
| R3-205033 | Support of Basic Mobility with Service Continuity | Ericsson |
| R3-205120 | Discussion on service continuity between MBS-capable cells | CATT |
| R3-205242 | Consideration on basic mobility in NR MBS | ZTE |
| R3-205243 | Consideration on service continuty of basic mobility in NR MBS | ZTE |
| R3-205351 | Consideration on Mobility with Service Continuity | LG Electronics |
| R3-205443 | MBS mobility with service continuity | CMCC |
| R3-205498 | CB: # 17_MBS_Mobility_SvcCont - Summary of email discussion | Ericsson - moderator |
| R3-205499 | CB: # 18_MBS_Mobility_SvcCont_CPUP - Summary of email discussion | Nokia - moderator |
| R3-205506 | CB: # 39_MBS_UP_count - Summary of email discussion | Lenovo - Moderator |
| 22.3.2 | Dynamic Change Between PTP and PTM with Service Continuity | |
| R3-204692 | Dynamic switch between PTP and PTM | Huawei |
| R3-204705 | Dynamic PTM and PTP switching | Qualcomm Incorporated |
| R3-204846 | Key Principles for PtP-PtM Switching | Nokia, Nokia Shanghai Bell |
| R3-204887 | Mobility support for the switching between PTP and PTM | vivo |
| R3-204921 | Mode Decision and Dynamic Switching between PTM and PTP | Lenovo, Motorola Mobility |
| R3-205034 | On NG-RAN support for dynamic change between PTP and PTM with service continuity | Ericsson |
| R3-205121 | Discussion on Uu mode selection in disaggregated gNBs | CATT |
| R3-205244 | Discussion about the procedure of delivery mode switching | ZTE |
| R3-205245 | Discussion about the bearer configuration for dlivery mode switching | ZTE |
| R3-205253 | Switching between multicast and unicast in RAN | LG Electronics |
| R3-205367 | Consideration on F1 MBS Transport Mode | CATT |
| R3-205398 | Dynamic Change Between PTP and PTM with Service Continuity | Samsung |
| R3-205500 | CB: # 19_MBS_PTP-PTM_DynChange - Summary of email discussion | Samsung - moderator |
| 22.3.3 | Dynamic Control of the Broadcast/Multicast Transmission Area | |
| R3-204693 | Dynamic Control of the MBS Transmission Area | Huawei |
| R3-204923 | 5G MBS Transmission Mode and Area Control | Lenovo, Motorola Mobility |
| R3-205035 | Dynamic Control of Broadcast/Multicast Transmission Area | Ericsson |
| R3-205246 | Discussion on multicast/broadcast transmission area | ZTE |
| R3-205247 | Dynamic transmission area control in CU/DU split scenario | ZTE |
| R3-205365 | Consideration on MBSFN Transmission Area | CATT |
| R3-205366 | Consideration on Transmission Area for SC-PTM | CATT |
| R3-205424 | Consideration on Dynamic Control of the Broadcast/Multicast Transmission Area | LG Electronics |
| R3-205501 | CB: # 20_MBS_DynTXareaCtrl - Summary of email discussion | Ericsson - moderator |
| R3-205685 | CB: # 20_MBS_DynTXareaCtrl - Summary of email discussion | Ericsson - moderator |
| 22.4 | Others | |
| R3-204886 | Counting the MBS interest | vivo |
| R3-205036 | On mobility to and from non-supporting NG-RAN nodes | Ericsson |
| R3-205248 | Consideration on the control information in NR MBS | ZTE |
| R3-205502 | CB: # 22_MBS_Counting - Summary of email discussion | Vivo - moderator |
| R3-205503 | CB: # 23_MBS_Mobility2NonSupporting - Summary of email discussion | Ericsson - moderator |
| R3-205504 | CB: # 21_MBS_CtrlInfo - Summary of email discussion | ZTE - moderator |
| R3-205686 | CB: # 22_MBS_Counting - Summary of email discussion | Vivo - moderator |
| R3-205687 | CB: # 23_MBS_Mobility2NonSupporting - Summary of email discussion | Ericsson - moderator |
| R3-205688 | CB: # 21_MBS_CtrlInfo - Summary of email discussion | ZTE - moderator |
| 30 | Other WIs/SIs Impacting RAN3 | |
| R3-204670 | Work plan for Rel-17 Additional enhancements for NB-IoT and LTE-MTC | Huawei, Ericsson |
| R3-204671 | Work plan for Rel-17 WI Further Multi-RAT Dual-Connectivity enhancements | Huawei |
| R3-204726 | Work Plan for NR IIoT/URLLC | Rapporteur (Nokia) |
| 31.2.1 | Reporting Per-Beam Measurements and SFTD Inter-RAT Results in LPPa | |
| R3-204653 | Support beam level inter-RAT measurement report in E-CID measurement in LPPa | NTT DOCOMO, INC. |
| R3-204654 | Support beam level inter-RAT measurement report in E-CID measurement in LPPa | NTT DOCOMO, INC., Ericsson |
| R3-204655 | Support beam level inter-RAT measurement report in E-CID over LPPa | NTT DOCOMO INC., Ericsson |
| R3-204656 | Introducing NR beam level measurement in inter-RAT measurement in E-CID measurement over LPPa | NTT DOCOMO INC., Ericsson |
| R3-205606 | Introducing NR beam level measurement in inter-RAT measurement in E-CID measurement over LPPa | NTT DOCOMO INC., Ericsson |
| 31.2.2 | Others | |
| R3-204607 | SCTP association change when current SCTP association is failed (X2) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-204657 | Addition of EN-DC connected indication in E-CID measurement response message over LPPa | NTT DOCOMO INC. |
| R3-204658 | Addition of EN-DC connected indication in Inter-RAT measurement result of E-CID measurement | NTT DOCOMO INC. |
| R3-204659 | Addition of NR CGI in Inter-RAT measurement result of E-CID measurement over LPPa | NTT DOCOMO INC., Ericsson |
| R3-204661 | Addition of EN-DC connected indication in E-CID measurement response message over LPPa | NTT DOCOMO INC. |
| R3-204847 | Correction of LTE-M Indication | Nokia, Nokia Shanghai Bell |
| R3-205284 | Corrections to 37.473 on encoding PLMNs in served cell information | Huawei, China Unicomm, Orange |
| R3-205285 | Miscellaneous clean-ups to 37.473 | Huawei, China Unicomm, Orange |
| R3-205286 | Correction to 37.473 on PWS related procedure | Huawei, China Unicomm, Orange |
| R3-205607 | CB: # 79_EncodingPLMNsW1 - Summary of email discussion | Huawei - moderator |
| R3-205608 | Corrections to 37.473 on encoding PLMNs in served cell information | Huawei, China Unicomm, Orange |
| R3-205609 | Correction to 37.473 on PWS related procedure | Huawei, China Unicomm, Orange |
| R3-205610 | SCTP association change when current SCTP association is failed (X2) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-205611 | CB: # 81_EN-DCinfo_E-CID - Summary of email discussion | NTT DOCOMO- moderator |
| R3-205778 | SCTP association change when current SCTP association is failed (X2) | Nokia, Nokia Shanghai Bell, China Telecom |
| 31.3.1 | X2 Support for UE CLI Measurement for EN-DC | |
| R3-204856 | On X2 support for UE CLI measurement for EN-DC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-204857 | Support for UE CLI measurement for EN-DC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-205187 | Support for UE CLI Measurement for MR-DC | ZTE |
| R3-205188 | 37340 CR to Support for UE CLI Measurement for MR-DC | ZTE |
| R3-205189 | X2AP CR to Support for UE CLI Measurement for MR-DC | ZTE |
| R3-205190 | XnAP CR to Support for UE CLI Measurement for MR-DC | ZTE |
| R3-205614 | CB: # 82_CLImeasEN-DC - Summary of email discussion | Nokia - moderator |
| R3-205745 | Support for intended TDD configuration transfer for EN-DC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| 31.3.2 | Node Name Format | |
| R3-204783 | Correction to node name format | Ericsson, Verizon Wireless, Samsung, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-204784 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-204785 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-204786 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung, China Telecom |
| R3-205191 | E1AP Corrections to node name type | ZTE |
| R3-205192 | F1AP Corrections to node name type | ZTE |
| R3-205193 | NGAP Corrections to node name type | ZTE |
| R3-205278 | Further discussions on node name type | Huawei |
| R3-205279 | Corrections to 38.473 on node name type | Huawei |
| R3-205280 | Corrections to 38.413 on node name type | Huawei |
| R3-205615 | CB: # 83_NodeNameType - Summary of email discussion | Ericsson - moderator |
| R3-205746 | Corrections to 38.473 on node name type | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-205747 | Corrections to 38.413 on node name type | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-205748 | Corrections to 38.463 on node name type | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| 31.3.3 | Direct Data Forwarding Between NG-RAN and E-UTRAN | |
| R3-204635 | Support of direct data forwarding for inter-system HO | China Telecom, CATT,Nokia , Nokia Shanghai Bell, ZTE |
| R3-204701 | PDU numbering in case of direct data forwarding from SN to the target node | Nokia, Nokia Shanghai Bell |
| R3-204712 | Direct data forwarding from source node to target SgNB in NR SA to EN-DC inter-system handover | Qualcomm Incorporated |
| R3-204727 | TS38.423 Support of 5G Intra-System Direct DF with Shared Source gNB | ZTE,CATT,China Telecom,China Unicom |
| R3-204848 | Support of Direct Data Forwarding for Inter-System Handover | Nokia, Nokia Shanghai Bell, CATT, China Telecom, ZTE |
| R3-204849 | Inter-system direct forwarding with shared en-gNB/gNB | Nokia, Nokia Shanghai Bell, Samsung, CATT, China Telecom, Huawei, Ericsson |
| R3-204958 | Enabling direct data forwarding for inter-RAT HO with SN-terminated bearers | Nokia, Nokia Shanghai Bell |
| R3-205086 | Direct data forwarding for inter-system handover over E1 | Huawei |
| R3-205087 | Direct data forwarding for inter-system handover over E1 | Huawei |
| R3-205088 | Direct data forwarding for inter-system handover over E1 | Huawei |
| R3-205102 | Discussion on E1AP for inter-system direct data forwarding | CATT, Nokia, Nokia Shanghai Bell, China Telecom, ZTE |
| R3-205103 | Support of inter-node handover with a shared split (S)gNB | CATT, Nokia, Nokia Shanghai Bell, China Telecom, ZTE |
| R3-205229 | Multiple forwarding tunnels signaling over E1 | Ericsson |
| R3-205230 | Multiple forwarding tunnels signaling over E1 | Ericsson |
| R3-205231 | Multiple forwarding tunnels signaling over E1 | Ericsson |
| R3-205382 | Direct data forwarding for Inter-system HO in CP-UP seperation | Samsung |
| R3-205383 | Support direct data forwarding for inter-system handover | Samsung |
| R3-205616 | CB: # 84_DirectDataFwdPDUnumbering - Summary of email discussion | Nokia - moderator |
| R3-205617 | CB: # 85_DirectDataFwdE1Impacts - Summary of email discussion | CATT - moderator |
| R3-205720 | TS38.423 Support of 5G Intra-System Direct DF with Shared Source gNB | ZTE,CATT,China Telecom,China Unicom |
| R3-205721 | CB: # 84bis_5GintraSysDirectDataFwdSharedSrcgNB - Summary of email discussion | ZTE - moderator |
| R3-205760 | Support of direct data forwarding for inter-system HO | China Telecom, Samsung, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Lenovo, Lenovo, Motorola Mobility |
| 31.3.4 | Full Slot Format Support for Intended TDD UL-DL Configuration | |
| R3-204709 | Slot list length correction in TDD UL-DL Configuration | Qualcomm Incorporated |
| R3-204710 | Full slot format support | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei |
| R3-204711 | Full slot formats support in Intended TDD UL-DL Configuration | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei |
| R3-205194 | Half Slot Format Support for Intended TDD UL-DL Configuration | ZTE |
| R3-205195 | CR for Half Slot Format Support for Intended TDD UL-DL Configuration | ZTE |
| R3-205618 | Slot list length correction in TDD UL-DL Configuration | Qualcomm Incorporated, ZTE |
| R3-205619 | CB: # 86_FullSlotSupportTDD - Summary of email discussion | Qualcomm - moderator |
| R3-205731 | [DRAFT] LS on Full slot formats support in TDD UL-DL configuration | Qualcomm Incorporated |
| R3-205794 | LS on Full slot formats support in TDD UL-DL configuration | Qualcomm Incorporated |
| R3-205803 | Slot list length correction in TDD UL-DL Configuration | Qualcomm Incorporated, ZTE |
| 31.3.5 | MDT for Inactive UEs | |
| R3-204915 | MDT configuration overriding issue | Huawei |
| R3-205037 | Signalling Logged MDT configuration indication | Ericsson |
| R3-205038 | Signalling Logged MDT configuration indication over NGAP TP | Ericsson |
| R3-205039 | Signalling Logged MDT configuration indication over XnAP | Ericsson |
| R3-205196 | Management based MDT should not overwrite signaling based MDT | ZTE |
| R3-205197 | NGAP management based MDT should not overwrite signaling based MDT | ZTE |
| R3-205198 | XnAP management based MDT should not overwrite signaling based MDT | ZTE |
| R3-205199 | LS-out management based MDT should not overwrite signaling based MDT | ZTE |
| R3-205399 | Discussion on the MDT for inactive UE | Samsung |
| R3-205400 | MDT for inactive UE | Samsung |
| R3-205401 | MDT for inactive UE | Samsung |
| R3-205620 | CB: #87_MDTinactive - Summary of email discussion | Ericsson - moderator |
| R3-205753 | MDT for inactive UE | Samsung |
| R3-205754 | MDT for inactive UE | Samsung |
| 31.3.6 | X2 Mapping Procedure for RACS | |
| R3-204876 | RACS in X2/Xn and UE Radio ID Capability Mapping procedure in X2 | NEC |
| R3-204877 | UE Radio ID Capability Mapping procedure in X2 | NEC |
| R3-204992 | Introducing UE Radio Capability Mapping procedure for EN-DC | Huawei |
| R3-204993 | Introducing UE Radio Capability Mapping procedure for EN-DC | Huawei |
| R3-204994 | Introducing UE Radio Capability Mapping procedure for EN-DC | Huawei |
| R3-205068 | Introducing UE Radio Capability ID Mapping procedure | Ericsson |
| R3-205069 | Introducing X2AP UE Radio Capability ID Mapping procedure | Ericsson |
| R3-205070 | Introducing X2AP UE Radio Capability ID Mapping procedure | Ericsson |
| R3-205135 | Discussion on X2 mapping procedure for RACS | CATT |
| R3-205136 | CR for TS36.423 support of X2 mapping for RACS | CATT |
| R3-205137 | CR for TS37.340 support of X2 mapping for RACS | CATT |
| R3-205138 | CR for TS36.300 support of X2 mapping for RACS | CATT |
| R3-205363 | Introducing UE Radio Capability Mapping procedure for EN-DC | Huawei |
| R3-205621 | CB: # 88_X2mappingRACS - Summary of email discussion | Ericsson - moderator |
| R3-205675 | Introducing UE Radio Capability Mapping procedure for EN-DC | Huawei |
| R3-205676 | Introducing UE Radio Capability Mapping procedure for EN-DC | Huawei |
| R3-205752 | Introducing UE Radio Capability ID Mapping procedure | Ericsson, NEC, Huawei, CATT, Samsung |
| 31.3.7.1 | Other Rel-16 Corrections | |
| R3-204636 | Discussion on Left issues of MLB in Release 16 | ZTE |
| R3-204637 | CR for TS 38.423 on Unsuccessful Operation and Abnormal Conditions of MLB | ZTE |
| R3-204638 | CR for TS 38.463 on Unsuccessful Operation and Abnormal Conditions of MLB | ZTE |
| R3-204639 | CR for TS 38.473 on Unsuccessful Operation and Abnormal Conditions of MLB | ZTE |
| R3-204640 | CR for TS 38.423 on Remaining Issue of MLB | ZTE |
| R3-204641 | CR for TS 38.473 on Remaining Issue of MLB | ZTE |
| R3-204651 | Correction on Industrial IOT Rel-16 DC+CA duplication for E1AP | ZTE, Intel Corporation, CATT, Ericsson, Huawei |
| R3-204652 | Correction on Industrial IOT Rel-16 DC+CA duplication for E1AP | ZTE, Intel Corporation, CATT, Ericsson, Huawei |
| R3-204672 | Further correction on fast MCG recovery via SRB3 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom, BT, China Telecom |
| R3-204673 | Further correction on fast MCG recovery via SRB3 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom, BT, China Telecom |
| R3-204674 | NPRACH configuration exchanging | Huawei, CMCC |
| R3-204675 | Exchanging of NB-IoT RLF report | Huawei, CMCC |
| R3-204676 | Exchanging of NB-IoT RLF report | Huawei, CMCC |
| R3-204677 | Correction on Coverage Enhancement Restrictions | Huawei, China Telecom |
| R3-204678 | Consideration on immediate suspension | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-204679 | Correction on immediate suspension | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-204696 | Add the support for updating RG Level Wireline Access Characteristics (NGAP) | Nokia, Nokia Shanghai Bell, Huawei, BT, Intel |
| R3-204697 | Add the support for updating RG Level Wireline Access Characteristics | Nokia, Nokia Shanghai Bell, Huawei, BT, Intel |
| R3-204699 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-204700 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-204713 | Correction on the configuration of subframe #0 and #5 for MCH in MBMS dedicated cell | Qualcomm Incorporated |
| R3-204716 | Alignment of values for maximum Integrity Protected Data Rate | Qualcomm Incorporated |
| R3-204717 | Alignment of values for maximum Integrity Protected Data Rate | Qualcomm Incorporated |
| R3-204718 | Alignment of values for maximum Integrity Protected Data Rate | Qualcomm Incorporated |
| R3-204729 | TS36.423 Corrections of SCG Suspend&Release Behaviors with EN-DC in Rel-16 | ZTE |
| R3-204769 | Discussion on One PDU session with Multiple CU-UPs | ZTE Corporation, China Telecom, CATT |
| R3-204770 | Support one PDU session with multiple CU-UPs for TS38.401 | ZTE Corporation, China Telecom, CATT |
| R3-204771 | Support one PDU session with multiple CU-UPs for TS38.413 | ZTE Corporation, China Telecom, CATT |
| R3-204787 | Corrections of procedures for PWS tests | Ericsson, One2many |
| R3-204788 | Draft LS on Test Procedures for PWS | Ericsson, One2many |
| R3-204793 | Mobility Restrictions in S-Node Addition procedure | Nokia, Nokia Shanghai Bell |
| R3-204810 | Introduction of 5GC Mobility Restriction List Container IE in S-Node Addition | Nokia, Nokia Shanghai Bell |
| R3-204850 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-204858 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-204859 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-204860 | Correction of NPN CAG cells and non-CAG cells | Nokia, Nokia Shanghai Bell, Orange |
| R3-204861 | Correction of NPN CAG cells and non-CAG cells | Nokia, Nokia Shanghai Bell, Orange |
| R3-204862 | Correction of NPN CAG cells and non-CAG cells | Nokia, Nokia Shanghai Bell, Orange |
| R3-204875 | UL Data Split | Nokia, Nokia Shanghai Bell |
| R3-204879 | Correction the NR Sidelink AMBR in ASN.1 definition | NEC |
| R3-204888 | TS38.463 Introduction of New Cause Value for gNB-CU-UP Initiated CHO Modify | ZTE, CATT, China Unicom |
| R3-204889 | Extend the usage of “Early Forwarding SN Transfer” procedure to DAPS HO | ZTE |
| R3-204890 | TS38.463 Extend the CHO Usage and Support Intra-SN/inter-UP CPC case | ZTE |
| R3-204891 | TS38.463 Extend the CHO Usage and Support Intra-SN/inter-UP CPC case | ZTE |
| R3-204900 | Clarification on TAI Slice Support List | China Telecommunication |
| R3-204901 | Clarification on TAI Slice Support List | China Telecommunication |
| R3-204903 | Support of RAN sharing for the disaggregated SNPN | China Telecommunication, Huawei, CATT |
| R3-204924 | Correction on Expected UE activity behaviour | Lenovo, Motorola Mobility |
| R3-204945 | Introducing AQP in path switch request acknowledge message | Huawei, Vodafone |
| R3-204946 | SON corrections | Huawei, CMCC |
| R3-204947 | SON corrections | Huawei, CMCC |
| R3-204948 | SON corrections | Huawei, CMCC |
| R3-204954 | Correction of Redundant Tunnel Setup | Nokia, Nokia Shanghai Bell |
| R3-204956 | Correction of Redundant Tunnel Setup | Nokia, Nokia Shanghai Bell |
| R3-204960 | Corrections on PC5 Link Aggregated Bit Rate | Ericsson, CATT, Intel Corporation |
| R3-204987 | Uniqueness of BH RLC channel ID | Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE |
| R3-204995 | Correction Ethernet Compression | Nokia, Nokia Shanghai Bell, Orange |
| R3-204996 | LS on Synchronization of Ethernet compression | Nokia, Nokia Shanghai Bell, Orange |
| R3-205040 | MRO Inter-system measurement Configuration | Ericsson |
| R3-205041 | MRO S1AP clarifications for Inter-system measurement Configuration | Ericsson |
| R3-205042 | Handling PDCP Duplication | Ericsson |
| R3-205043 | Handling PDCP Duplication | Ericsson |
| R3-205044 | Introduction of CPC Execution Completion in RRC Transfer | Ericsson |
| R3-205066 | Draft LS on broadcasting gNB ID length in system information block | Ericsson, Verizon |
| R3-205067 | Enabling usage of flexible NG-RAN Node ID length | Ericsson, Verizon |
| R3-205071 | Introduction of CPC Execution Completion in RRC Transfer | Ericsson |
| R3-205089 | Support of shared-DU and dedicated logical-CU for NPN | Huawei, China Telecom |
| R3-205090 | Introducing the secondary NG-RAN node ID in PDU Session Resource Modify Response message | Huawei, CATT, ZTE, Intel |
| R3-205091 | Clarification of Mobility Restriction List | Huawei, China Telecom |
| R3-205092 | Clarification of Mobility Restriction List | Huawei, China Telecom |
| R3-205093 | Correction of last PDU session release for SSC mode 2 | Huawei |
| R3-205094 | Introducing Additional Duplication Activation over E1 | Huawei, CATT |
| R3-205095 | Introducing updated CN PDB in path switch request acknowledge message | Huawei |
| R3-205104 | Correction on Radio Resource Status Metric | CATT |
| R3-205110 | Correction on PRACH coordination | CATT |
| R3-205122 | Correction on LTE UE RLF Report | CATT |
| R3-205123 | Correction on UE History Information | CATT |
| R3-205124 | Correction on ASN.1 for Failure Indication message | CATT |
| R3-205127 | Discussion on MRO for RRC re-connected cell | CATT |
| R3-205128 | Correction on inconsistent description for attempted and successful re-connected cell | CATT |
| R3-205142 | Early UE Capability Retrieval for eMTC | Qualcomm Incorporated |
| R3-205143 | Support for early retrieval of UE capabilities | Qualcomm Incorporated |
| R3-205144 | Support for early retrieval of UE capabilities | Qualcomm Incorporated |
| R3-205145 | Support for early retrieval of UE capabilities | Qualcomm Incorporated |
| R3-205148 | Correction of RAN CP Relocation | Nokia, Nokia Shanghai Bell |
| R3-205149 | Correction of ARP | Nokia, Nokia Shanghai Bell |
| R3-205150 | Correction of ARP | Nokia, Nokia Shanghai Bell |
| R3-205151 | Correction on V2X related information | Google Inc. |
| R3-205209 | Non-Monotonic Alternative QoS Parameter values | VODAFONE Group Plc |
| R3-205237 | SCTP port number allocatd by IANA | Orange |
| R3-205238 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange |
| R3-205239 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange |
| R3-205255 | Correction on the Maximum Number of CHO Preparations in X2AP | Samsung |
| R3-205256 | Correction on the Maximum Number of CHO Preparations in F1AP | Samsung |
| R3-205257 | Correction of the DAPS Response Information IE in the tabular | Samsung |
| R3-205258 | Discussion on CHO Trigger IE in the BEARER CNTX MODIFICATION REQUEST message | Samsung |
| R3-205261 | Addition of the CHO Trigger IE in the BEARER CONTEXT MODIFICATION REQUEST message | Samsung |
| R3-205262 | Clarifiation on the DAPS HO response per E-RABs | Samsung |
| R3-205263 | Clarifiation on the DAPS HO response per DRBs | Samsung |
| R3-205287 | PLMN Not Supported Cause Value | Nokia, Nokia Shanghai Bell |
| R3-205298 | Correction on IAB-DU configuration | Huawei |
| R3-205299 | Correction on unsuccessful operations of IAB procedures | Huawei |
| R3-205300 | Correction on the identification of IAB-donor-DU | Huawei |
| R3-205301 | Correction on the Context Setup procedure for IAB node | Huawei |
| R3-205302 | Correction on BAP address | Huawei |
| R3-205350 | Correction for Rel-16 NR Industrial IoT | Intel Corporation, CATT, Huawei, Ericsson |
| R3-205357 | Correction CR on Network instance for 38.413(R16) | CATT |
| R3-205358 | Correction CR on Network instance for 38.423(R16) | CATT |
| R3-205368 | CR to 38.473: Correction on gNB-DU Cell Resource Configuration | ZTE, Sanechips, Nokia |
| R3-205369 | CR to 38.463 Correction on IAB UP TNL Address Update | ZTE, Sanechips, Samsung |
| R3-205371 | Discussion on the LTE-NR Relative Timing indication over X2 | China Telecom, Qualcomm, ZTE |
| R3-205406 | Clarification of QoS Mapping Information over E1 for Rel-16 IAB | Samsung, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-205407 | CR on clarification of QoS Mapping Information over E1 for Rel-16 IAB | Samsung, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-205408 | Discussion on including gNB-DU ID for IAB UP TNL Address Update | Samsung |
| R3-205409 | CR on including gNB-DU ID for IAB UP TNL Address Update | Samsung |
| R3-205426 | CR to TS36.423 on the LTE-NR Relative Timing indication | China Telecom, Qualcomm Incorporated, ZTE |
| R3-205447 | Issue of intra gNB-CU-UP DAPS HO | CATT |
| R3-205448 | CR to TS 38463 for Intra gNB-CU-UP DAPS HO | CATT |
| R3-205528 | Correction of ARP | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-205529 | Correction of ARP | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-205556 | CR to 38.473: Correction on gNB-DU Cell Resource Configuration | ZTE, Sanechips, Nokia |
| R3-205557 | CR to 38.463 Correction on IAB UP TNL Address Update | ZTE, Sanechips, Samsung |
| R3-205622 | Further correction on fast MCG recovery via SRB3 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom, BT, China Telecom |
| R3-205623 | Further correction on fast MCG recovery via SRB3 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom, BT, China Telecom |
| R3-205624 | Correction on Industrial IOT Rel-16 DC+CA duplication for E1AP | ZTE, Intel Corporation, CATT, Ericsson, Huawei |
| R3-205648 | SON corrections | Huawei, CMCC |
| R3-205704 | CR on clarification of QoS Mapping Information over E1 for Rel-16 IAB | Samsung, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-205705 | Corrections on PC5 Link Aggregated Bit Rate | Ericsson, CATT, Intel Corporation |
| R3-205706 | CB: # 76bis_PC5_AggrBitRate - Summary of email discussion | Ericsson - moderator |
| R3-205707 | SON corrections | Huawei, CMCC |
| R3-205708 | Correction of NPN CAG cells and non-CAG cells | Nokia, Nokia Shanghai Bell, Orange |
| R3-205709 | Correction of NPN CAG cells and non-CAG cells | Nokia, Nokia Shanghai Bell, Orange |
| R3-205710 | Correction of NPN CAG cells and non-CAG cells | Nokia, Nokia Shanghai Bell, Orange |
| R3-205711 | CB: # 78bis_CAGcorrection - Summary of email discussion | Nokia - moderator |
| R3-205712 | CB: # 79bis_AddDuplActE1 - Summary of email discussion | Huawei - moderator |
| R3-205713 | Correction of Redundant Tunnel Setup | Nokia, Nokia Shanghai Bell |
| R3-205714 | Correction on IAB-DU configuration | Huawei |
| R3-205715 | CR for TS 38.423 on Unsuccessful Operation and Abnormal Conditions of MLB | ZTE |
| R3-205716 | CR for TS 38.463 on Unsuccessful Operation and Abnormal Conditions of MLB | ZTE |
| R3-205717 | CR for TS 38.473 on Unsuccessful Operation and Abnormal Conditions of MLB | ZTE |
| R3-205718 | TS38.463 Extend the CHO Usage and Support Intra-SN/inter-UP CPC case | ZTE |
| R3-205770 | CB: # 77bis_SONcorrections - Summary of email discussion | Huawei |
| R3-205787 | Correction of NPN CAG cells and non-CAG cells | Nokia, Nokia Shanghai Bell, Orange |
| R3-205788 | CB: # 78bis_CAGcorrection - Summary of email discussion | Nokia - moderator |
| R3-205799 | CR for TS 38.423 on Unsuccessful Operation and Abnormal Conditions of MLB | ZTE |
| R3-205800 | CR for TS 38.463 on Unsuccessful Operation and Abnormal Conditions of MLB | ZTE |
| R3-205801 | CR for TS 38.473 on Unsuccessful Operation and Abnormal Conditions of MLB | ZTE |
| 31.3.7.2 | Pure Stage-2 Rel-16 Corrections | |
| R3-204728 | TS37.340 Stage2 Refined Descriptions of SCG Suspend&Resume Operation | ZTE |
| R3-204916 | Correction on anonymization of MDT in EN-DC | Huawei |
| R3-205152 | Correction on conditional reconfiguration for PSCell | Google Inc. |
| R3-205154 | Correction on conditional reconfiguration for PSCell | Google Inc. |
| R3-205158 | Correction to SCG Resuming from suspension | Google Inc. |
| R3-205236 | DAPS data forwarding in stage-2 | Ericsson |
| R3-205240 | CHO in stage-2 | Ericsson |
| R3-205303 | Correction on IAB procedures | Huawei |
| R3-205304 | Correction on clarification of non-F1 traffic | Huawei, CATT, Samsung, Nokia, Nokia Shanghai Bell |
| R3-205384 | Issues in stage 2 on MRO | Samsung |
| R3-205385 | Correction on intra-system MRO | Samsung |
| R3-205532 | Correction on clarification of non-F1 traffic | Huawei, CATT, Samsung, Nokia, Nokia Shanghai Bell |
| 31.3.7.3 | Other TEI16 | |
| R3-204789 | Addition of Local NG-RAN Node Identifier to resolve NG-RAN ID from I-RNTI. | Ericsson |
| R3-204790 | Addition of Local NG-RAN Node Identifier. | Ericsson |
| R3-205505 | Response to R3-204789 and R3-204790 | Nokia, Nokia Shanghai Bell |
| 31.4 | Rapporteur Corrections for Rel-16 | |
| R3-204724 | NGAP tabular corrections and asn.1 review | Rapporteur (Nokia) |
| R3-204725 | Rapporteur cleanup of NGAP | Rapporteur (Nokia) |
| R3-204863 | Rapporteur Correction of 38.410 | Nokia, Nokia Shanghai Bell |
| R3-204864 | Rapporteur correction of 38.410 | Nokia, Nokia Shanghai Bell |
| R3-204865 | Rapporteur Correction of 38.415 | Nokia, Nokia Shanghai Bell |
| R3-204866 | Rapporteur correction of 38.415 | Nokia, Nokia Shanghai Bell |
| R3-204949 | Rapporteur Corrections | Huawei |
| R3-204950 | Rapporteur Corrections | Huawei |
| R3-204951 | Correction of procedure ID | Huawei |
| R3-204952 | Correction of PWS cancel | Huawei |
| R3-204953 | Correction of PWS cancel | Huawei |
| R3-205045 | Missing MeNB UE X2AP ID Extension IE in Trace messages | Ericsson |
| R3-205046 | Essential correction for Rel-16 LTE_feMob-Core WI | Ericsson |
| R3-205047 | Rapporteur’s corrections to TS 36.423 v16.2.0 | Ericsson |
| R3-205048 | Correction for the Interface Instance Indication in the EN-DC X2 SETUP RESPONSE message | Ericsson |
| R3-205049 | Rapporteur Corrections for NR SON MDT WI and IAB WI | Ericsson |
| R3-205050 | Missing ASN.1 of TNL Transport Layer Address Info IE in the EN-DC X2 SETUP RESPONSE message | Ericsson |
| R3-205051 | Correction CR0036 implementation – missing DRB-IDs-takenintouse in PDU Session Resource Setup Response Info - SN terminated | Ericsson |
| R3-205052 | Correction of CR0360 – Enabling an ng-eNB to reply to Cell Assistance Information E-UTRA. | Ericsson |
| R3-205053 | Correction of CR 0393r2 | Ericsson, CATT |
| R3-205054 | Correcting Target Cell List for Rel-16 mobility enhancements | Ericsson, Nokia, Nokia Shanghai Bell, Intel Corporation, Huawei |
| R3-205055 | Missing QoS Flow Mapping Indication IE in PDU Session Resource Modification Info – SN terminated IE. | Ericsson |
| R3-205056 | Rapporteur’s corrections to TS 38.423 v16.2.0 | Ericsson |
| R3-205057 | Restructurion FAILURE INDICATION message – avoid condition upon absence of IE | Ericsson |
| R3-205058 | Missing MeNB UE X2AP ID Extension IE in Trace messages | Ericsson |
| R3-205059 | Correction for the Interface Instance Indication in the EN-DC X2 SETUP RESPONSE message | Ericsson |
| R3-205060 | Correction CR0036 implementation – missing DRB-IDs-takenintouse in PDU Session Resource Setup Response Info - SN terminated | Ericsson |
| R3-205062 | Rapporteur Corrections to 38.401 | NEC |
| R3-205096 | Missing QoS Flow Mapping Indication IE in PDU Session Resource Modification Info – SN terminated IE. | Ericsson |
| R3-205227 | Rapporteur’s corrections for TS 38.463 | Ericsson |
| R3-205228 | Rapporteur’s editorial corrections for TS 38.463 | Ericsson |
| R3-205241 | Correction of asn.1 in NGAP Elementary Procedure List | Rapporteur (Nokia) |
| R3-205268 | Rapporteur cleanup of S1AP | Rapporteur (Nokia) |
| R3-205477 | CB: # 5_R16_RappCRs - Summary of email discussion | InterDigital - moderator |
| R3-205548 | Correction CR0036 implementation – missing DRB-IDs-takenintouse in PDU Session Resource Setup Response Info - SN terminated | Ericsson |
| R3-205549 | Correction CR0036 implementation – missing DRB-IDs-takenintouse in PDU Session Resource Setup Response Info - SN terminated | Ericsson |
| R3-205550 | Missing QoS Flow Mapping Indication IE in PDU Session Resource Modification Info – SN terminated IE. | Ericsson |
| R3-205558 | Rapporteur Corrections to 38.401 | NEC, Ericsson |
| R3-205559 | Rapporteur Corrections | Huawei |
| R3-205591 | Rapporteur correction of 38.410 | Nokia, Nokia Shanghai Bell |
| R3-205592 | Rapporteur correction of 38.415 | Nokia, Nokia Shanghai Bell |
| R3-205612 | Rapporteur’s corrections to TS 36.423 v16.2.0 | Ericsson |
| R3-205613 | Rapporteur Corrections for NR SON MDT WI and IAB WI | Ericsson |
| R3-205643 | Rapporteur cleanup of NGAP | Rapporteur (Nokia) |
| R3-205691 | Rapporteur’s corrections to TS 38.423 v16.2.0 | Ericsson |
| R3-205693 | Rapporteur’s corrections for TS 38.463 | Ericsson |
| R3-205699 | Correction of CR0360 – Enabling an ng-eNB to reply to Cell Assistance Information E-UTRA. | Ericsson |
| R3-205701 | correction of mandatory ProtocolExtensionContainer | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-205734 | Correction on protocol IE for MDTConfigurationNR | Ericsson, Nokia, Nokia Shanghai Bell |